[Bug 1875186] Re: Booting continues despite three failed attempts if the root partition is unencrypted

[Naël]

I now realize that the behavior I originally described in this report as
a bug is in fact appropriate: three tries to unlock an encrypted
partition at boot is apparently default, and startup can and should
continue even when the /home partition is not available, it just won't
be mounted in the /home mountpoint. As long as the operating system
itself is on unencrypted/unlocked partitions, it can run just fine
without any user home directory.

Amusingly, I can even log in in a virtual console, I'm just dropped into
/ since /home is empty.

Closing this report as Invalid - not a bug.

** Changed in: cryptsetup (Ubuntu)
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to cryptsetup in Ubuntu.
https://bugs.launchpad.net/bugs/1875186

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

Status in cryptsetup package in Ubuntu:
  Invalid

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1875186/+subscriptions