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.
-- no keyboard input on plymouth SSL password prompt https://bugs.launchpad.net/bugs/602255 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
