Cryptoapi/aes-cipher

Top Page
Attachments:
Message as email
+ (text/plain)
Delete this message
Reply to this message
Author: david uhlman
Date:  
Subject: Cryptoapi/aes-cipher
It has to do with the ciphers built in to redhat 9, it only includes
standard aes, module cipher-aes.o . If you want the feature where you
can hash a password to 128 or 256 bit and hence longer the 20
characters and can include spaces, use the redhat 8 losetup rpm I
mentioned before (Note that the hashing occurs in losetup though). Or
recompile the kernel to incorporate the other ciphers.

Sincerely,
David Uhlman
CTO 50KM Inc.

On Mon, 2003-09-01 at 00:10, Kitty wrote:
> On Sun, 2003-08-31 at 16:15, david uhlman wrote:
> > util-linux-2.11y-9aes.i686.rpm
> > mount-2.11y-9aes.i686.rpm
> > losetup-2.11y-9aes.i686.rpm
>
> OK, installed the above, (rpm -e'd the old mount/losetup pkgs), and they
> seemed good so far. Upon testing:
>
> [root@moo etc]# dd if=/dev/urandom of=/etc/test-aes bs=1024K count=5
> 5+0 records in
> 5+0 records out
> [root@moo etc]# losetup -e aes /dev/loop1 /etc/test-aes
> Password:
> Error: Password must be at least 20 characters.
> [root@moo etc]# losetup -e aes /dev/loop1 /etc/test-aes
> Password:
> ioctl: LOOP_SET_STATUS: Invalid argument
>
> So I 'rpmbuild --recompile'd the .src.rpm package, and got the same
> error.
>
> This is where I'm at now. System is RH9 w/ kernel 2.4.20-20.9 & Ximian2
> desktop. Will reboot into 2.4.20-8 and try it there.
>
> Also, I'm kind of curious about the 20 character password requirement,
> which sort of defeats the purpose of feeding the password directly into
> AES. It wasn't like that before.
>
> Thanks for all your work so far.