hi,
i have a few questions and hope someone can help me to find the
answers...
i'm using the kerneli patch for 2.4.18 and the loopback patch from hvr.
both (crypto and loopback) built-in into the kernel (i386). i didn't
need to recompile losetup and mount because the system defaults of them
worked like a charm (at least i guess so). i'm using latest debian sid.
1) is there is a way to specify the aes encryption with whatever key
length over the command line? like:
losetup -e aes128 /dev/loop0 crypto
because this gives the error:
The cipher does not exist, or a cipher module needs to be loaded into
the kernel
ioctl: LOOP_SET_STATUS: Invalid argument
but my /proc/crypto/cipher/ shows:
-r--r--r-- 1 root root 0 Mar 11 03:28 aes-cbc
-r--r--r-- 1 root root 0 Mar 11 03:28 aes-ecb
if i only give the following line losetup asks me which key length i
want to use:
losetup -e aes /dev/loop0 crypto
Available keysizes (bits): 128 192 256
Keysize:
this way i can't use the '-p' option of losetup to get the passwd over
file descriptor. and that's bad.....
2) is there a way to find out if the given passwd is correct or not
before trying to mount the fs and notice that mounting fails because of
bad passwd? something like....
mount: wrong fs type, bad option, bad superblock on /dev/loop0,
or too many mounted file systems
3) is there a way to change the passwd? because for example if the user
has the same passwd as the login passwd and now someone find out the
passwd. what now???? is the only solution for this creating a new crypto
file and copying all it's content from one to an other?
thanks a lot in advance,
best regards,
alias m96.
-
Linux-crypto: cryptography in and on the Linux system
Archive: http://mail.nl.linux.org/linux-crypto/
