[Bug 1225136] Re: 13.10 regression: No password asked for encrypted partitions during boot
Steve Langasek
steve.langasek at canonical.com
Sun Sep 15 20:47:12 UTC 2013
> Using the defaults.
Yes, but the defaults will result in a different boot experience
depending on the hardware and the driver configuration. Are you using
binary drivers? Do you get the text experience that I describe - where
typing causes the passphrase prompt to show up after having been
overwritten - or do you get something else? Is there any chance you
could take a picture of what you're getting on boot?
> My password contains letter "m", and whenever I reach it, it goes into
> Manual recovery mode.
Ok, I certainly can't reproduce this. With either the graphical or the
text frontend, the passphrase prompt takes precedence over the "press S
or M" prompt, as expected/designed.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to cryptsetup in Ubuntu.
https://bugs.launchpad.net/bugs/1225136
Title:
13.10 regression: No password asked for encrypted partitions during
boot
Status in “cryptsetup” package in Ubuntu:
Incomplete
Bug description:
# cat /etc/crypttab
home /dev/sda3 none luks
# cat /etc/fstab
...
/dev/mapper/home /home ext4 defaults 0 0
During boot, there's a message that /home isn't ready or not present.
Skip or Manual recovery
Expected: prompt me for password
This works:
cryptsetup luksOpen /dev/sda3 home; mount /home
13.04 used to work with same setup (and it also detected the encrypted
partition during install, and set it up for me. 13.10 ignores it)
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: cryptsetup-bin 2:1.4.3-4ubuntu4
ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0
Uname: Linux 3.11.0-5-generic x86_64
ApportVersion: 2.12.1-0ubuntu4
Architecture: amd64
Date: Fri Sep 13 21:25:13 2013
InstallationDate: Installed on 2013-09-13 (0 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130909)
MarkForUpload: True
SourcePackage: cryptsetup
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1225136/+subscriptions
More information about the foundations-bugs
mailing list