Public bug reported:
Binary package hint: initscripts
This was an upgrade install of Karmic alpha 5 from an up-to-date Jaunty.
I have an unencrypted boot, an encrypted root, and a separate encrypted
/home partiton.
In Jaunty, on boot, I would be prompted once each for the passwords for
the two encrypted partitions (root first, then home), and once booting
was complete, both partitions would be accessible.
In Karmic, on boot I am prompted once each for the passwords for the two
encrypted partitions, but after booting is complete, the /home partition
is not mounted, though it is decrypted.
After booting, this problem can be worked around by running either of
the following commands as root using sudo. There is no prompt for
encryption password (this is why I believe the partition is decrypted
during the boot process):
mount -a
/etc/init.d/mountall.sh start
I am reporting this against initscripts because /etc/init.d/mountall.sh
is a component of that package, and if run on boot (as I would expect
would typically happen, being in /etc/init.d) mountall.sh would
presumaby mount the partition if operating correctly.
I am not ticking the 'security' box because the only security issue I
can think of is a corner case that is not an issue in my situation.
Specifically, if the user does not pay attention, an encrypted disk may
be available unencrypted but not mounted. An unobservant user may only
check to see if the encrypted partition is mounted, and assume that it
is not encrypted if not mounted.
Additional information:
1) Description: Ubuntu karmic (development branch)
Release: 9.10
2) initscripts:
Installed: 2.86.ds1-61ubuntu16
Candidate: 2.86.ds1-61ubuntu16
Version table:
*** 2.86.ds1-61ubuntu16 0
500 http://us.archive.ubuntu.com karmic/main Packages
100 /var/lib/dpkg/status
3) above
4) above
** Affects: sysvinit (Ubuntu)
Importance: Undecided
Status: New
** Tags: boot cryptsetup disk mount
--
Separate encrypted home decrypted but not mounted automatically on boot.
https://bugs.launchpad.net/bugs/427596
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
