Boot p/w prompt enter key failures
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| ecryptfs-utils (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
1. With ecryptsfs:
/etc/fstab:
/root/ecfs_data /root/ecfs ecryptfs rw,exec,suid 0 0
a) Pressing the enter key quickly with no other input returns that some input is required.
b) Pressing the enter key the first time subsequent to some input appears to append a return character to the password string. Pressing the enter subsequent to that submits the now incorrect password resulting in failure.
c) If you hold the enter key, it sends multiple return characters, some times some of them appear to be appended to the password string, until eventually they start being sent to subsequent prompts. It would appear that sometimes multiple return characters are added to the password string because the signatures change on various attempts.
c) may be relevant in the sense that the holding the enter key in #2 facilitates a workaround.
2. The following may look like it is unrelated but consider the fact that the password prompt is not halted and the fact that this should in fact work.
The reason why I think the following is related is because I think that it's possible that it is returning from the password prompt and failing the crypttab execution asynchronously if that is perhaps how the relevant executables (upstart?) operate.
/etc/crypttab:
swap_e /dev/sda8 /dev/urandom swap
/etc/fstab:
/dev/mapper/swap_e none swap sw 0 0 #<-- if this is before the next line, it specifies that /dev/mapper/swape does not exist, and auto returns from the ecryptfs password prompt
/root/ecfs_data /root/ecfs ecryptfs rw,exec,suid 0 0
As specified, when the ecryptfs mount entry in fstab is after the swap mount, it specifies that the /dev/mapper/swape disk does not exist and auto skips the ecryptfs mount, auto returning from the password prompt and said mount failure in /var/log/boot.log.
System:
Ubuntu 12.04.3 LTS
ecryptfs-utils 96-0ubuntu3
| MetaChrome (imagenesis) wrote | #1 |
I was not aware, one could specify multiple packages that a bug affects as it appears these can only be added subsequent to a bug report as opposed to in the bug creation workflow.
A bug report that specifies other affected packages is here. I am not sure if this is an issue caused by ecryptfs, but it would be convenient to have a workaround provided by ecryptfs and other affected packages if the issue cannot be resolved at a dependency level.
https:/