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 19/07/18 19:05, laurent cop wrote:
> Hello,
> 
> - I am working on debian9, not connected to internet.(repo is not accessible)
> - I have download cryptsetup-2.0.3 (tar.xz)
> - I have execute configure, make, make install script
> 
> - I try cryptsetup --version => 2.0.3
> - I try cryptsetup --benchmark
>     I cannot see this algo, in fact I see most of my previous version 1.7 only
> 
> - crypsetup -v luksFormat --type luks2 /dev/mydev --cipher aes-gcm-random --integrity aead
>     => Enter passphrase
>    => verify
>  device-mapper: table: 253:0: integrity: unknow target type

So you have old kernel that does not support dm-integrity.

If you read man page, there is note that you need to use kernel 4.12.

(The detection is quite tricky, because module is autoloaded quite late
but we should probably make error message more clear here.)

m.


> device-mapper: ioctl; error adding target to table
> device-mapper: reload ioctl on failed : invalid argument
> Cannot format integrity for device /dev/mydev
> Command failed with code -1
> 
> How can I check if my
> 
> 
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@xxxxxxxx
> https://www.saout.de/mailman/listinfo/dm-crypt
> 
_______________________________________________
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