Booting continues despite three failed attempts if the root partition is unencrypted

Bug #1875186 reported by Naël
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cryptsetup (Ubuntu)
New
Undecided
Unassigned

Bug Description

On a computer with an unencrypted root partition and an encrypted /home partition, during boot, after three failed attempts to unlock the /home partition, startup proceeds and I end up at GDM. I cannot log in though, since /home is still locked.

I expected cryptsetup to either keep asking for the passphrase or refuse to proceed and ask me to power off instead.

Is it a bug? Is it the desired behavior? Does it make the computer less secure than the unencrypted / partition already does (I realize that it is a bad setup)?

PS: The 60 second delay reported in bug 1862660 doesn't happen.

Ubuntu 20.04, cryptsetup 2:2.2.2-3ubuntu2

information type: Private Security → Public Security
information type: Public Security → Public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.