tomb

commit 7a98ee8ba64885c1161958956d8f2fd2e6413380
parent 4439a6a327f69371782f481e3ee2d455c6517aa7
Author: Jaromil <jaromil@dyne.org>
Date:   Sat, 21 Jan 2017 23:47:16 +0100

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.

Diffstat:
M
tomb
 | 
2
+-

1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tomb b/tomb
@@ -1508,7 +1508,7 @@ forge_key() {
     { option_is_set --use-urandom } && random_source=/dev/urandom
 
     _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 ]] || {
         _warning "Cannot generate encryption key."
         _failure "Operation aborted." }