better integrate with plymouth

Bug #1124186 reported by Dimitri John Ledkov
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
cryptsetup (Ubuntu)
Confirmed
Wishlist
Unassigned

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.

Changed in cryptsetup (Ubuntu):
importance: Undecided → Wishlist
status: New → Confirmed
Revision history for this message
Steve Langasek (vorlon) wrote : Re: [Bug 1124186] [NEW] better integrate with plymouth

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.

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.