no keyboard input on plymouth SSL password prompt

Bug #602255 reported by Boris Devouge on 2010-07-06
30
This bug affects 4 people
Affects Status Importance Assigned to Milestone
upstart (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: upstart

Steps to reproduce:
Install Ubuntu 10.04 LTS, install apache and apache ssl, create a certificate for SSL, protect the certificate with a passphrase.
Reboot the machine.

Results:
Graphical console (Plymouth) display a password entry field ... however no keyboard input make it impossible to continue boot sequence, and apache is never started.

Expected results:
Keyboard input works at password prompt, Apache SSL is started, boot sequence finishes normally.

Tom Ellis (tellis) wrote :

I can confirm this bug.

Very easy to reproduce, only way I can see to work around it is to boot rescue mode and remove the password from the key.

Rob Dyke (emailme-robdyke) wrote :

/me too.

We can't remove the password as we have business requirement for manual entry of password for key.

Related to this issue is that, post boot, if one starts an upstart job (service xxx start) for a daemon that requires a password for a private key, the i/o of the daemon is of course inherited from upstart itself, and hence the user never receives the prompt, at least not from where he starting the job (such as for example from a ssh login). I do not suggest a solution for this, I am just noting that there is an additional scenario where this can be problematic.

Tom Ellis (tellis) on 2010-07-15
Changed in upstart (Ubuntu):
status: New → Confirmed
Clint Byrum (clint-fewbar) wrote :

I believe this is basically a duplicate of bug #582963, which was recently "fixed" in natty by using plymouth's ask-for-pass.

Unfortunately, that breaks automatic boot, and so may not be acceptable for SRU.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers