[Bug 1124186] [NEW] better integrate with plymouth

[Steve Langasek]

On Wed, Feb 13, 2013 at 02:48:41PM -0000, Dmitrijs Ledkovs wrote:
> Currently cryptroot handles number-of-tries by itself, maybe it's better
> to use plymouth api with --command.

> Currently there is a noticeable delay between typing a passphrase wrong
> & being offered to type it again. But maybe it's just cryptsetup taking
> it's time.

Principally, I didn't do this originally because it makes for a significant
change to the internal API of cryptdisks.functions.  There are already open
bug reports about the fact that Ubuntu's cryptsetup divergence from
Debian/upstream breaks non-plymouth-based passphrase prompting; I think we
should fix that bug, rather than making the problem worse by breaking all
other values of $KEYSCRIPT.

-- 
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/1124186

Title:
  better integrate with plymouth

Status in “cryptsetup” package in Ubuntu:
  Confirmed

Bug description:
  Options for ask-for-password command:
    --command=<string>             Command to send password to via standard input
    --prompt=<string>              Message to display when asking for password
    --number-of-tries=<integer>    Number of times to ask before giving up (requires --command)
    --dont-pause-progress          Don't pause boot progress bar while asking

  Currently cryptroot handles number-of-tries by itself, maybe it's
  better to use plymouth api with --command.

  Currently there is a noticeable delay between typing a passphrase
  wrong & being offered to type it again. But maybe it's just cryptsetup
  taking it's time.

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