Re: are cryptoapi and loop-aes compatible

[Christopher Schadl <cschadl@satan.org.uk>]

On 2002.11.01 11:19 Jari Ruusu wrote:
> Tom Vier wrote:
> > or did i just forget my passphrase? what about the stuff in 2.5? is
> it
> > compatable with the other loopback crypto implementations?
> 
> Loop-AES and kerneli.org-cryptoapi use same on-disk format, but
> userspace
> tools need different options. To mount AES encrypted volumes created
> with
> kerneli.org-cryptoapi in loop-AES, use mount option -o phash=rmd160 or
> losetup option -H rmd160, and specify cipher name as AES128, AES192 or
> AES256.

I've been trying to access some of my old data encrypted with cryptoapi 
2.4.7.0 (compiled with the loop IV-mode patch) and while I am able to 
mount the encrypted image by passing -o phash=rmd160 to mount, the data 
contained on the filesystem is unreadable, no doubt due to the 
differences in block-size values.  Is it possible to mount data 
encrypted with cryptoapi 2.4.x.x with loop-aes by passing an 'offset' 
or 'blocksize' option to mount?
-
Linux-crypto:  cryptography in and on the Linux system
Archive:       http://mail.nl.linux.org/linux-crypto/