Re: problem with aes-256 after software upgrade

[Jari Ruusu <jariruusu@xxxxxxxxxxxxxxxxxxxxx>]

lists@xxxxxxxxxxxxxx wrote:
> first losetup segfaulted and then:
> 
> MHC:root@linux:/var/src/util-linux-2.12a/mount# ./losetup -a
> Segmentation fault
> MHC:root@linux:/var/src/util-linux-2.12a/mount# lsmod | grep loop
> loop                   57420  1
> 
> module is not removable again

> echo $PW | $GPG | ./losetup -e AES256 -p 0 /dev/loop0 /cf/xcf0
> 
> i get:
> 
> ioctl: LOOP_CLR_FD: No such device or address
> 
> but when i do "losetup -a" i get:
> 
> /dev/loop0: [0303]:7454729 (/cf/xcf0) encryption=AES256
> 
> but /dev/loop0 is still unusable :((((

Above looks like loop.ko module was compiled for wrong kernel configuration.

After you compile your kernel, you need to compile loop.ko without moving or
cleaning compiled kernel source tree. Something like this:

    cd /usr/src/linux-2.6.6
    mv .config z
    make distclean
    mv z .config
    make oldconfig
    make dep && make clean && make bzImage
    make modules && make modules_install
    cat arch/i386/boot/bzImage >/boot/vmlinuz
    cp System.map /boot/System.map-2.6.6

    cd /usr/src/loop-AES-v2.1c
    make LINUX_SOURCE=/usr/src/linux-2.6.6

If you are using lilo bootloader, you need to run lilo:

    lilo

And then reboot to new kernel /boot/vmlinuz

-- 
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/