* Depend on watershed.
* cryptdisks.functions: do_tmp should mount under /var/run/cryptsetup for
changing the permissions of the filesystem root, not directly on /tmp,
since mounting on /tmp a) is racy, b) confuses mountall something fierce.
LP: #475936.
* debian/cryptdisks.functions:
- wrap the call to /lib/cryptsetup/askpass with watershed, to make sure
we only ever have one of these running at a time; otherwise multiple
invocations could steal each other's input and/or write over each
other's output
- new function, crypttab_start_one_disk, to look for the named source
device in /etc/crypttab (by device name, UUID, or label) and start it
if configured to do so
* debian/cryptdisks-udev.upstart: new, additional upstart job run once for
each block device, using the new crypttab_start_one_disk function,
triggered by udev; this doesn't eliminate the possibility of a race with
gdm when the decrypted volume isn't a 'bootwait' mount point (since gdm
kills usplash), but it does eliminate the race between udev and
cryptsetup. LP: #454898.
The other cryptdisks-enable job is still needed as well, to give us the
second pass needed to cover devices that are decrypted using keys stored
on other encrypted disks. LP: #443980.
* debian/cryptdisk.functions: initially create the device under a temporary
name and rename it only at the end using 'dmsetup rename', to ensure that
upstart/mountall doesn't see our device before it's ready to go.
LP: #475936.
* Make the 'start' action of the init script a no-op, this should be
handled entirely by the upstart job now; ad remove any symlinks from
/etc/rcS.d on upgrade. LP: #473615.
-- Steve Langasek <email address hidden> Tue, 22 Dec 2009 23:29:32 +0000
This bug was fixed in the package cryptsetup - 2:1.0.6+ 20090405. svn49-1ubuntu7. 2
--------------- 6+20090405. svn49-1ubuntu7. 2) karmic-proposed; urgency=low
cryptsetup (2:1.0.
* Depend on watershed. functions: do_tmp should mount under /var/run/cryptsetup for
* cryptdisks.
changing the permissions of the filesystem root, not directly on /tmp,
since mounting on /tmp a) is racy, b) confuses mountall something fierce.
LP: #475936.
cryptsetup (2:1.0. 6+20090405. svn49-1ubuntu7. 1) karmic-proposed; urgency=low
* debian/ cryptdisks. functions: /askpass with watershed, to make sure start_one_ disk, to look for the named source cryptdisks- udev.upstart: new, additional upstart job run once for start_one_ disk function, cryptdisk. functions: initially create the device under a temporary mountall doesn't see our device before it's ready to go.
- wrap the call to /lib/cryptsetup
we only ever have one of these running at a time; otherwise multiple
invocations could steal each other's input and/or write over each
other's output
- new function, crypttab_
device in /etc/crypttab (by device name, UUID, or label) and start it
if configured to do so
* debian/
each block device, using the new crypttab_
triggered by udev; this doesn't eliminate the possibility of a race with
gdm when the decrypted volume isn't a 'bootwait' mount point (since gdm
kills usplash), but it does eliminate the race between udev and
cryptsetup. LP: #454898.
The other cryptdisks-enable job is still needed as well, to give us the
second pass needed to cover devices that are decrypted using keys stored
on other encrypted disks. LP: #443980.
* debian/
name and rename it only at the end using 'dmsetup rename', to ensure that
upstart/
LP: #475936.
* Make the 'start' action of the init script a no-op, this should be
handled entirely by the upstart job now; ad remove any symlinks from
/etc/rcS.d on upgrade. LP: #473615.
-- Steve Langasek <email address hidden> Tue, 22 Dec 2009 23:29:32 +0000