On 09/01/2014 11:35 PM, Sven Eschenberg wrote: > Here's the CRYPTO config of the kernel that works with old cryptsetup: > > CONFIG_CRYPTO=y > CONFIG_CRYPTO_ALGAPI=y > CONFIG_CRYPTO_ALGAPI2=y > CONFIG_CRYPTO_AEAD2=y > CONFIG_CRYPTO_BLKCIPHER=y > CONFIG_CRYPTO_BLKCIPHER2=y > CONFIG_CRYPTO_HASH=y > CONFIG_CRYPTO_HASH2=y > CONFIG_CRYPTO_RNG2=y > CONFIG_CRYPTO_PCOMP2=y > CONFIG_CRYPTO_MANAGER=y > CONFIG_CRYPTO_MANAGER2=y > CONFIG_CRYPTO_GF128MUL=y > CONFIG_CRYPTO_WORKQUEUE=y > CONFIG_CRYPTO_CBC=y > CONFIG_CRYPTO_XTS=y > CONFIG_CRYPTO_RMD160=y > CONFIG_CRYPTO_SHA1=y > CONFIG_CRYPTO_SHA256=y > CONFIG_CRYPTO_AES=y > CONFIG_CRYPTO_AES_586=y > ----- > What I added to get to the passphrase for current cryptsetup is: > CONFIG_CRYPTO_ANSI_CPRNG=y > CONFIG_CRYPTO_USER_API=y <= AF_ALGO > CONFIG_CRYPTO_USER_API_HASH=y > CONFIG_CRYPTO_USER_API_SKCIPHER=y > ---- > > The Volume is AES-XTS-plain and the hashspec sha1 > > I can't see what might be missing ... If you can send which exact kernel version it is and full .config, which fails I can try to reproduce it. Thanks, Milan _______________________________________________ dm-crypt mailing list dm-crypt@xxxxxxxx http://www.saout.de/mailman/listinfo/dm-crypt
