change forged key lenght to 512 bits

Addresses issue #238: as 512 bit key length triggers use of AES256.
Apparently so far tombs used AES128 due to key length 256.
Change passes all tests and has no regression implications.
This commit is contained in:
Jaromil 2017-01-21 23:47:16 +01:00
parent 4439a6a327
commit 7a98ee8ba6

2
tomb
View File

@ -1508,7 +1508,7 @@ forge_key() {
{ option_is_set --use-urandom } && random_source=/dev/urandom { option_is_set --use-urandom } && random_source=/dev/urandom
_verbose "Data dump using ::1:: from ::2 source::" ${DD[1]} $random_source _verbose "Data dump using ::1:: from ::2 source::" ${DD[1]} $random_source
TOMBSECRET=$(${=DD} bs=1 count=256 if=$random_source) TOMBSECRET=$(${=DD} bs=1 count=512 if=$random_source)
[[ $? == 0 ]] || { [[ $? == 0 ]] || {
_warning "Cannot generate encryption key." _warning "Cannot generate encryption key."
_failure "Operation aborted." } _failure "Operation aborted." }