slackware cryptoAPI

[rinonapo]

As I have read in the manual from my slackware 10.1 I issued

# dd if=/dev/urandom of=/dev/hdb1 bs=1M count=20
20+0 records in
20+0 records out

then I type

#losetup /dev/loop2 /dev/hdb1 -e aes
Password:
ioctl: LOOP_SET_STATUS: Invalid argument


What does that mean???? on boot the cryptoAPI is already insalled and started
by default on slackware 10.1!!!!!!

[rinonapo]

no ideas?

[puntmuts]

Maybe this will help:
http://www.ibiblio.org/pub/Linux/doc...oop-HOWTO.html

[rinonapo]

Ok I'll give it a through read.... but I'm thinking one thing...
why don't linux boxes come with complete system and data loop encryption....? So many law problems??

[rinonapo]

Well what I did was reconfigure my 2.4 kernel for encryption but the shell stll spits out the error message

ioctl: LOOP_SET_STATUS: Invalid argument

what's wrong.. all modules where correctly loaded.. I also tried to load them not as modules but nothing...

[rinonapo]

I've tried all the steps again with a new 2.6 kernel and this time I don't get the ioctl error... instead

root@luwrr:/home/pkkle# losetup -e blowfish /dev/loop0 crypt.iso
/dev/loop0: No such device or address

root@hkh,k:/home/bkkk# losetup -e blowfish /dev/loop1 crypt.iso
/dev/loop1: No such file or directory

Note the different error message between dev/loop0 and /dev/loop1
It looks so damn difficult to set it up