[Bug 1104156] [NEW] "Continue to wait, or Press S to skip mounting or M for manual recovery" when waiting for LUKS passphrase

Launchpad Bug Tracker 1104156 at bugs.launchpad.net
Thu Jan 24 16:29:19 UTC 2013


You have been subscribed to a public bug by Ubuntu Foundations Team Bug Bot (crichton):

Hello,

(On Quantal) When using passphrase-protected LUKS encryped partition,
'mountall' shows the "Continue to wait, or Press S to skip mounting or M
for manual recovery" after the (hardcoded) 3-second BOREDOM_TIMEOUT.

This is:
 - inappropriate as long as a passphrase is being prompted for
 - useless since the prompt intercepts the key presses (and prevents the S or M option to be used)
 - inelegant (any potentially misleading)

I first thought of adding a mountpoint-specific option to disable
boredom messages for appropriate mountpoints. But adding yet-another
option to the mountpoint stanza somehow seemed wrong.

On the other hand, if cryptsetup fails after several passphrase attemps,
one should still be given the choice to Skip or Manually recover the
partition.

I don't know how to handle a "state" tracking between 'cryptsetup' and
'mountall', so that 'mountall' does not get bored as long as a
passphrase is being prompted for.

The best way I found to make that issue less "invasive" is to allow the
boredom timeout to being extended (globally) when a particular system
setup requires it.

I thus attach a patch that allows to change the boredom timeout to the
"dev_wait_time" (or ROOTDELAY, if it is undefined) via a new '--be-
patient' option and configuration variables in /etc/default/mountall.

Corresponding patched Quantal 'mountall' package should be available
shortly from https://launchpad.net/~cedric.dufour/+archive/ppa/

Hope it can help.

** Affects: mountall (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: patch
-- 
"Continue to wait, or Press S to skip mounting or M for manual recovery" when waiting for LUKS passphrase
https://bugs.launchpad.net/bugs/1104156
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.



More information about the Ubuntu-sponsors mailing list