Comment 10 for bug 468208

This bug is still present. It is present not only on crypttab password prompts but also on /ecryptfs password prompts.

Encryption on boot with password is utterly broken because of this, and likely any other input at boot.

1. This issue still absolutely remains with the cryptsetup password prompts.
2. With ecryptfs, even though it appears that nothing has stolen the keyboard focus (ie data does not appear to be printed past the Password: semicolon) the string that is actually sent from the password prompt is incorrect. Pressing the enter key either does not do anything or it sends the enter key as a character in the password prompt.
3. This behavior also quite possibly messes up upstart event loop as evidenced by the following behavior:

If a mount of ecryptfs is after a mount of a swap from a cryptsetup unencrypted /dev/mapper, it specifies that /dev/mapper disk does not exist.

http://askubuntu.com/questions/387529/how-to-enable-crypttab-to-run-at-boot
http://askubuntu.com/questions/387463/how-to-decrypt-encryptfs-at-boot

As specified, when the ecryptfs mount entry in fstab is after the swap mount, it specifies that the disk does not exist and completely skips the ecryptfs mount without prompting for the password or recording said failure in /var/log/boot.log.

This is a critical bug. How has this been festering for 4 years. Does no one mount decrypt at boot?

Utter failure canonical.