[ Steve Langasek ]
* debian/initramfs/cryptroot-script: if plymouth is present in the
initramfs, use this directly, bypassing the cryptsetup askpass script;
but keep support for these other frontends around on a transitional
basis.
* debian/cryptdisks.functions:
- change interaction to use plymouth directly if present, and if not, to
fall back to /lib/cryptsetup/askpass as before
- 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-enable.upstart: run the upstart job 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
plymouth), but it does eliminate the race between udev and cryptsetup.
LP: #454898.
* debian/cryptdisks-enable.upstart: check that the package is installed
and exit gracefully if it's not. LP: #435814
* 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.
[ Colin Watson ]
* Add ext4 support to passdev.
-- Steve Langasek <email address hidden> Tue, 15 Dec 2009 18:05:45 -0800
This bug was fixed in the package cryptsetup - 2:1.1.0~ rc2-1ubuntu4
--------------- 0~rc2-1ubuntu4) lucid; urgency=low
cryptsetup (2:1.1.
[ Steve Langasek ] initramfs/ cryptroot- script: if plymouth is present in the cryptdisks. functions: /askpass as before /askpass with watershed, to make sure start_one_ disk, to look for the named source cryptdisks- enable. upstart: run the upstart job once for each block start_one_ disk function, triggered by udev; cryptdisks- enable. upstart: check that the package is installed cryptdisk. functions: initially create the device under a temporary mountall doesn't see our device before it's ready to go.
* debian/
initramfs, use this directly, bypassing the cryptsetup askpass script;
but keep support for these other frontends around on a transitional
basis.
* debian/
- change interaction to use plymouth directly if present, and if not, to
fall back to /lib/cryptsetup
- 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/
device, using the new crypttab_
this doesn't eliminate the possibility of a race with gdm when the
decrypted volume isn't a 'bootwait' mount point (since gdm kills
plymouth), but it does eliminate the race between udev and cryptsetup.
LP: #454898.
* debian/
and exit gracefully if it's not. LP: #435814
* debian/
name and rename it only at the end using 'dmsetup rename', to ensure that
upstart/
LP: #475936.
[ Colin Watson ]
* Add ext4 support to passdev.
-- Steve Langasek <email address hidden> Tue, 15 Dec 2009 18:05:45 -0800