better integrate with plymouth
Bug #1124186 reported by
Dimitri John Ledkov
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=
--prompt=<string> Message to display when asking for password
--number-
--dont-
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 |
To post a comment you must log in.
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 functions. There are already open
change to the internal API of cryptdisks.
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.