Jan Lühr wrote: > In nearly every multi-key example a keyfile with 65 keys is used. Why do you > use exactly 65 keys? Because version 3 on-disk format requires 65 keys. README section 2.6. > Every example I see in the docs uses AES128. Is there a reason not to use > AES256? (Of cource AES-128 will be secure for some time, but this is a reason > pro aes-128 and not against aes-256, because AES-256 is also for some time ;) AES128 is a little bit faster than AES256 > Example 2 uses a lot of head / tail stuff to manipulate the /dev/urandom > output. Why do I need this? Key file needs 65 random keys, each separated by newline. The head / tail pipe strips away uuencode header and footer which are _not_ random. -- Jari Ruusu 1024R/3A220F51 5B 4B F9 BB D3 3F 52 E9 DB 1D EB E3 24 0E A9 DD - Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/
