You are not logged in.
Hi
A couple of month ago I installed Arch in a VM using lvm on top of a partition eyncrypted with dm-crypt. After I did a full system upgrade today - I hadn't been using this installation for a longer time - my passphrase now gets rejected at startup ("No key available with this passphrase.") If I use the fallback boot option I can boot using that very passphrase.
What did I do wrong/what went wrong and how can I fix this?
TIA
Last edited by zebulone (2010-06-18 23:17:39)
Offline
Same issue here.
It seems that after the prompt for the passphrase, only a single character is read as the password. No way to type the full password. It was working perfectly last friday. Here are the packages that have been updated since then:
nspluginwrapper-debian (1.3.0-1 -> 1.3.0-1)
nspluginwrapper-flash (10.1.53-1)
libao (1.0.0-1 -> 1.0.0-2)
coreutils (8.5-1 -> 8.5-2)
sdl (1.2.14-4 -> 1.2.14-5)My computer hasn't been restarted yet, because my ~ is mounted with crypsetup and I fear I won't be able to login if the problem remains after a reboot.
Idea anyone ?
Aurélien.
EDIT: I tried to reboot and it works now.
Last edited by aurelieng (2010-06-20 14:46:51)
Offline
I don't know if this is your problem, but if you're using a piped key then it may be this bug...
http://www.saout.de/pipermail/dm-crypt/ … 00799.html
which appear with the cryptsetup upgrade 1.1.0 to 1.1.2. This regression bug has been fixed in the dev version, but won't be likely fixed in the repos until cryptsetup > 1.1.2 The solution is to roll back to cryptsetup 1.1.0.
Also have a look here
http://code.google.com/p/cryptsetup/issues/list
Offline