Re: cryptsetup : LUKS2 Issue for using cryptsetup --type with aes-gcm-random

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 25/07/18 19:39, laurent cop wrote:
> Hello,
> 
> I have upgraded my kernel to 4.16, I am on Debian 9
> 
> Nevertheless I received this error :
> 
> root@NAS:/home/user1# cryptsetup --debug luksFormat --type luks2 /dev/nvme3n1p1 --cipher aes-gcm-random --integrity aead
> 
> # cryptsetup 2.0.3 processing "cryptsetup --debug luksFormat --type luks2 /dev/nvme3n1p1 --cipher aes-gcm-random --integrity aead"

The command is correct, but I expect something is missing in your kernel.

> # Trying to format INTEGRITY device on top of /dev/nvme3n1p1, tmp name temporary-cryptsetup-954e81ee-a612-4cdb-b82a-5567abc01fc4, tag size 28.
> # dm version   [ opencount flush ]   [16384] (*1)
> # dm versions   [ opencount flush ]   [16384] (*1)
> # Detected dm-ioctl version 4.37.0.

Here it should also print version of dm-crypt and dm-integrity targets (kernel modules).

Do you have these device-mapper target compiled in and available?

Could you post output of "dmsetup targets" after it fails?

I will add some better error message here, but detection what is available
is more complicated that it seems...

Milan
_______________________________________________
dm-crypt mailing list
dm-crypt@xxxxxxxx
https://www.saout.de/mailman/listinfo/dm-crypt




[Index of Archives]     [Device Mapper Devel]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Packaging]     [Fedora SELinux]     [Yosemite News]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux