On 19/10/2019 17:29, Fourhundred Thecat wrote: > On 19/10/2019 16.41, Michael Kjörling wrote: >> On 19 Oct 2019 13:44 +0200, from 400thecat@xxxxxx (Fourhundred Thecat): >>>> This is the first problem - why you do not have kernel userspace crypto API enabled? >>> >>> What is the name of the CONFIG_ option of the kernel userspace crypto API ? >> >> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/crypto/Kconfig?h=v4.14.146#n16 >> indicates that it should be CONFIG_CRYPTO. You'll probably need some >> others as well, depending on how you actually plan to use LUKS. At an >> absolute minimum, I would expect you'd need one of the >> CONFIG_CRYPTO_AES variants as well as CONFIG_CRYPTO_SHA1 when running >> the LUKS utilities with defaults (AES, SHA1). > > that is weird. I have all those crypto options in the kernel: Strange, if you run "cryptsetup benchmark", does it calculate speed of the block ciphers section? (The same kernel user API is used here.) cryptsetup benchmark -c aes-xts-plain64 -s 512 Milan _______________________________________________ dm-crypt mailing list dm-crypt@xxxxxxxx https://www.saout.de/mailman/listinfo/dm-crypt
