This bug was fixed in the package cryptsetup - 2:2.0.2-1ubuntu1
---
cryptsetup (2:2.0.2-1ubuntu1) bionic; urgency=low
* Merge from Debian unstable.
- bugfix upstream release, which solves problems with luks2 format
disks not unlocking. LP: #1755322.
* Remaining changes:
** Changed in: cryptsetup (Ubuntu)
Importance: Undecided => High
** Changed in: cryptsetup (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1755322
Title:
log
All passwords accepted.
I'll try to submit to Ubuntu.
Jim
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1755322
Title:
logging in with luks2 converted encrypted disk only accepts keylsot #1
pass
Thx. So, the keyslot 2 was not converted, but added later once device
was already in luks2 mode.
Anyway, all offsets and parameters look correct, I was able to recreate
the same sized device and it works for me (with upstream git, 2.0.2+).
Can you try from command line for each slot and passphras
8 3:25 AM
To: jhem...@hotmail.com
Subject: [Bug 1755322] Re: logging in with luks2 converted encrypted disk only
accepts keylsot #1 password
Could you attach luksDump output?
--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/17553
LUKS header information
Version:2
Epoch: 3
Metadata area: 12288 bytes
UUID: 45e55b5c-b1f4-425c-9021-373b0a12e571
Label: (no label)
Subsystem: (no subsystem)
Flags: (no flags)
Data segments:
0: crypt
offset: 2097152 [bytes]
length
Could you attach luksDump output?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1755322
Title:
logging in with luks2 converted encrypted disk only accepts keylsot #1
password
To manage notificati
