Okay, got the makefile fixed (I think) and it compiles and boots
and loads all the crypto at boot like it should. I also chose the IV
mode sector, although now I'm not sure that was a good idea. Also
patched util-linux and now losetup can work with all the cyphers. Still
seems to be some problems, however. I did a test run with just the
examples on the losetup man page:
> dd if=/dev/zero of=/file bs=1k count=100
> losetup -e blowfish /dev/loop0 /file
> Password :
> mkfs -t ext2 /dev/loop0 100
>
> mount -t ext2 /dev/loop0 /mnt
>
except I used aes and chose a 128 bit key. Mounted it okay and could
read and write to it. Unmounted it and tried to mkreiserfs on it, but
reiser said it was too small and that wouldn't work.
So then I did a losetup -d on it and started over, this time
with a bs=100K count=512, but now I get a kernel error like someone else
had mentioned a bit a go,
> Sep 6 14:22:18 cybershamanix kernel: Unable to handle kernel NULL pointer deref
> erence at virtual address 00000000
> Sep 6 14:22:18 cybershamanix kernel: printing eip:
> Sep 6 14:22:18 cybershamanix kernel: c027aa97
> Sep 6 14:22:18 cybershamanix kernel: *pde = 00000000
> Sep 6 14:22:18 cybershamanix kernel: Oops: 0000
> Sep 6 14:22:18 cybershamanix kernel: CPU: 0
> Sep 6 14:22:18 cybershamanix kernel: EIP: 0010:[blowfish_set_key+231/432]
> Sep 6 14:22:18 cybershamanix kernel: EFLAGS: 00010282
> Sep 6 14:22:18 cybershamanix kernel: eax: 00000000 ebx: 00000004 ecx: 9b878
> 3a8 edx: 00000000
> Sep 6 14:22:18 cybershamanix kernel: esi: 00000000 edi: 00000011 ebp: c5f69
> f2c esp: c5f69df0
> Sep 6 14:22:18 cybershamanix kernel: ds: 0018 es: 0018 ss: 0018
> Sep 6 14:22:18 cybershamanix kernel: Process losetup (pid: 2428, stackpage=c5f6
> 9000)
> Sep 6 14:22:18 cybershamanix kernel: Stack: c5f86a1c 00000000 c0107020 c5f86014
> c5f8605c c5f86014 c0309820 c5f86a1c
> Sep 6 14:22:19 cybershamanix kernel: c0309820 c5f69ef9 c5f86000 c5f69ecc
> c0275cf6 c5f86000 c5f69f2c 00000020
> Sep 6 14:22:19 cybershamanix kernel: 00000000 c0275ee7 c5f86000 c5f69f2c
> 00000020 c5f86000 00000000 fffffff4
> Sep 6 14:22:19 cybershamanix kernel: Call Trace: [ret_from_intr+0/7] [default_s
> et_key+22/32] [cryptoapi_status+151/208] [loop_init_xfer+40/80] [loop_set_status
> +233/448]
> Sep 6 14:22:19 cybershamanix kernel: [lo_ioctl+440/448] [blkdev_ioctl+38/64]
> [sys_ioctl+115/416] [system_call+51/64]
> Sep 6 14:22:19 cybershamanix kernel:
> Sep 6 14:22:19 cybershamanix kernel: Code: 8b 04 96 31 c8 89 04 96 89 da 89 d0
> 8b 4d d8 c1 fa 1f 41 f7
>
and, if I try to run losetup of any kind, even losetup -d on the loop0,
or on a loop1 instead, that term session locks up. I can't even kill the
old losetup job from another term session, have to reboot to get rid of
them.
So, is my klutziness in setting it up or the IV, or what?
--
Harmon Seaver, MLIS
CyberShamanix
Work 920-203-9633 hseaver@xxxxxxxxxxxxxxxxx
Home 920-233-5820 hseaver@xxxxxxxxxxxxx
http://www.cybershamanix.com/resume.html
Linux-crypto: cryptography in and on the Linux system
Archive: http://mail.nl.linux.org/linux-crypto/
