[ubuntu/karmic-proposed] cryptsetup 2:1.0.6+20090405.svn49-1ubuntu7.1 (Accepted)

[Steve Langasek]

cryptsetup (2:1.0.6+20090405.svn49-1ubuntu7.1) karmic-proposed; urgency=low

  * 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.

Date: Wed, 04 Nov 2009 02:51:37 -0800
Changed-By: Steve Langasek <steve.langasek at ubuntu.com>
Maintainer: Ubuntu Core Developers <ubuntu-devel-discuss at lists.ubuntu.com>
Signed-By: Steve Langasek <steve.langasek at canonical.com>
https://edge.launchpad.net/ubuntu/karmic/+source/cryptsetup/2:1.0.6+20090405.svn49-1ubuntu7.1
-------------- next part --------------
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Wed, 04 Nov 2009 02:51:37 -0800
Source: cryptsetup
Binary: cryptsetup cryptsetup-udeb
Architecture: source
Version: 2:1.0.6+20090405.svn49-1ubuntu7.1
Distribution: karmic-proposed
Urgency: low
Maintainer: Ubuntu Core Developers <ubuntu-devel-discuss at lists.ubuntu.com>
Changed-By: Steve Langasek <steve.langasek at ubuntu.com>
Description: 
 cryptsetup - configures encrypted block devices
 cryptsetup-udeb - configures encrypted block devices (udeb)
Changes: 
 cryptsetup (2:1.0.6+20090405.svn49-1ubuntu7.1) karmic-proposed; urgency=low
 .
   * 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.
Checksums-Sha1: 
 454e7d37f445d4017bc455fe4e024b9dd0fa7b2a 1622 cryptsetup_1.0.6+20090405.svn49-1ubuntu7.1.dsc
 f16785f70e3a0ef311f0641e067d63f43f1764ad 445301 cryptsetup_1.0.6+20090405.svn49-1ubuntu7.1.diff.gz
Checksums-Sha256: 
 ddbc43b4b0dbfa97a71cbaef9bc4d10aec6e26956974201a6c93a03b877c0b6b 1622 cryptsetup_1.0.6+20090405.svn49-1ubuntu7.1.dsc
 801718bd27dd8c9567b491b6130f12bfe0c1119fa8903ada456f3f245f28fc72 445301 cryptsetup_1.0.6+20090405.svn49-1ubuntu7.1.diff.gz
Files: 
 a53ca15308adfda79c847bc5ff6b41f3 1622 admin optional cryptsetup_1.0.6+20090405.svn49-1ubuntu7.1.dsc
 f6677b1e72c5d4e783bd988e191133c4 445301 admin optional cryptsetup_1.0.6+20090405.svn49-1ubuntu7.1.diff.gz
Launchpad-Bugs-Fixed: 443980 454898 473615 475936
Original-Maintainer: Debian Cryptsetup Team <pkg-cryptsetup-devel at lists.alioth.debian.org>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iD8DBQFLKKRLKN6ufymYLloRAh5JAKDGOKVLMAHF0q9NJUSZ8fcpfyoYEQCeIgF2
g2/XvtK0ztni4GOx43iMPdQ=
=Q3zt
-----END PGP SIGNATURE-----