I just noticed that I made a typo in my above posting, it is
/dev/mapper/cryptotmp that is not ready on boot, and thus does not get
mounted properly.
--
Karmic boot doesn't wait for encrypted disc passphrase
https://bugs.launchpad.net/bugs/468885
You received this bug notification because you are
I have a similar issue, although I am mounting my encrypted home drive via
pam_mount, so those seem ok. However I have an encrypted tmp and swap
configured using crypttab.
#
cryptohome /dev/md0 none noauto,luks
cryptoswap /dev/sdd2 /dev/urandom
cipher=aes-cbc-essiv:sha256,si
I was seeing a similar problem, but I figured out what I was doing wrong. On
my system my window manager, compiz, was capturing the keypress and it was
launching the gnome-terminal. By changing which terminal compiz launches, I am
getting the correct terminal started when I press my hotkey.
I spent some more time messing around with my system and I am now able to get
my home drive to mount when I log in. I had to modify my /etc/crypttab
settings.
However I am still getting the use_first_pass message.
Darin
On Sat, 25 Apr 2009 16:30:40 -
Per Ångström wrote:
> I think I have
I upgraded to Ubuntu 9.04 and I am also seeing this message. x86_64
However I also use pam_mount to mount a luks encrypted home drive, and
it looks like logging in no longer passes my login password to
cryptsetup (that is, what use_first_pass is supposed to do). Both gdm
and a terminal based lo
