Re: LUKS2 AES-GCM-random erroring with key size issue.
Michael Kjörling <michael-/[email protected]>
| Newsgroups | gmane.linux.kernel.device-mapper.dm-crypt |
|---|---|
| Message-ID | <vjrndhcxkdzfmjznvkfzt7t7@localhost> |
On 27 Feb 2020 05:37 +0000, from [email protected] (vinay paduru): > Could you please help us solve this problem. > > # cryptsetup --verbose luksFormat --type luks2 --cipher aes-gcm-random --integrity aead /dev/sdb2 > [...] > Cipher aes-gcm-random (key size 256 bits) is not available. Try running the same command with --debug and send the full output of that. The exact kernel and cryptsetup version and build you're using (including distribution package version, if applicable), and the contents of /proc/crypto immediately after running cryptsetup, might also be useful. Especially if you're building from source, it's also a good idea to double-check that the cryptsetup binary that you're running is the one you expect. -- Michael Kjörling • https://michael.kjorling.se • [email protected] “Remember when, on the Internet, nobody cared that you were a dog?” _______________________________________________ dm-crypt mailing list [email protected] https://www.saout.de/mailman/listinfo/dm-crypt