Re: different instructions for use with aes256?

[Bradley Worley <geekysuavo@xxxxxxxxx>]

that code seems to work just fine, since almost all examples on the
net use either 2925 bytes from /dev/random or 2880 bytes.  however, i
guess if you really want to be picky you can up it to 5850 bytes
(double 2925), since you are technically doubling your key sizes. 
(it's a wild guess, really.)

  ~ brad.

On 10/25/05, Marvin Lyndon <marvin.lyndon@xxxxxxxxxxx> wrote:
> Hi all,
>
> I have successfully followed all the steps in the loop-AES readme file.
> Since I couldn't find any reference to this, I would like to know whether
> the step in which one creates the 65 random keys
>
> head -c 2925 /dev/random | uuencode -m - | head -n 66 | tail -n 65 \
> | gpg --symmetric -a >/a/usbstick/keyfile.gpg
>
> needs any modification for use in AES256 mode. Or is it enough to replace
> all occurrences of AES128 with AES256 as one follows the README file?
>
> Thanks for any help
>
> Marv
>
> _________________________________________________________________
> FREE pop-up blocking with the new MSN Toolbar – get it now!
> http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/
>
>
> -
> Linux-crypto:  cryptography in and on the Linux system
> Archive:       http://mail.nl.linux.org/linux-crypto/
>
>
Š{±r¼©¶‡+Ê›h‚¶©‡(§jwhžØ^.)îÆ̬µé€­Èb½èm¶Ÿÿ™¨¥žYbžìh®åŠ{±r¼©¶?