[gentoo-security] crypto problem mount loop0

[i.t]

hi,

for months I've been successfully working with cryptoloop on a cryptfile with 
a gento 2.4.22-gss kernel;
some days ago I've updated the baselayout for the system and lateron I 
couldn't start losetup anymore.
I've recompiled the kernel,
installed gentoo kernel 2.6.3,
and for comparison on a fedora partition loop-AES-v2.0f.
rm -f -r test-file[1234] test-dir1
*** Test results ok ***

So far I get the following results with gentoo kernel2.6.3 and patched fedora 
(2.4.22):

losetup -e AES /dev/loop0 crfile
Passwort:
[ok]
mount /dev/loop0 /mnt/loop/
mount: you must give the filesystem (Sie muessen den Dateisystemtyp angeben)

I'm pretty sure the filesystem was ext3 for the crfile (ok - meanwhile I know 
ext2 is better),
but when I try:

mount -t ext3 /dev/loop0 /mnt/loop/
mount:
(Falscher Dateisystemtyp, ungÃŒltige Optionen, der
       »Superblock« von /dev/loop0 ist beschÀdigt oder es sind
       zu viele Dateisysteme eingehÀngt)
wrong filesystem, invalid options, or superblock is damaged...

this goes for every filesystem type what is supported.
With gentoo 2.4.22-gss #4 SMP I get these results:

losetup -e aes /dev/loop0 DorAES
Password:
ioctl: LOOP_SET_STATUS: Invalid argument

I'm a bit desperated after all the time and work. What may have happenend?
Has anybody any idea? Can there be a change in the offset size with losetup?
Any help really appreciated

thanks
-- 
 . ___
 |  | 
 |  |  
       

--
gentoo-security@g.o mailing list