--hash argument ignored when creating a luks2 volume
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cryptsetup (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Command used to create a luks2 volume:
cryptsetup luksFormat /dev/loop0 --type luks2 --hash sha512
Output of luksDump shows pbkdf2 is still using sha256
The problem has been resolved in version 2.2.0 cryptsetup:
https:/
[root@mtz ink]# cryptsetup luksDump /dev/loop0
LUKS header information
Version: 2
Epoch: 3
Metadata area: 12288 bytes
UUID: 19642715-
Label: (no label)
Subsystem: (no subsystem)
Flags: (no flags)
Data segments:
0: crypt
offset: 4194304 [bytes]
length: (whole device)
cipher: aes-xts-plain64
sector: 512 [bytes]
Keyslots:
0: luks2
Key: 256 bits
Priority: normal
Cipher: aes-xts-plain64
PBKDF: argon2i
Time cost: 4
Memory: 872450
Threads: 4
Salt: 73 63 6a 10 5a a8 48 a6 f8 5a fa 2b 63 52 8e d0
AF stripes: 4000
Area offset:32768 [bytes]
Area length:131072 [bytes]
Digest ID: 0
Tokens:
Digests:
0: pbkdf2
Hash: sha256
Iterations: 94705
Salt: 77 ef 94 fa bb ae 54 b6 59 1e b8 75 c0 c1 c0 f9
Digest: b1 6c 4d 09 d6 b2 92 d9 64 83 37 23 3f e0 5f c0
[root@mtz ink]#
required change seems to be https:/ /gitlab. com/cryptsetup/ cryptsetup/ commit/ cdb4816fbbc814a 856006b0e9d40ad 435019eedf