Accepted:
cryptsetup 2:1.0.5-2ubuntu2 was ACCEPTED.
        Component: main Section: admin

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Thu, 11 Oct 2007 19:51:58 +0200
Source: cryptsetup
Binary: cryptsetup cryptsetup-udeb
Architecture: source
Version: 2:1.0.5-2ubuntu2
Distribution: gutsy
Urgency: low
Maintainer: Ubuntu MOTU Developers <[EMAIL PROTECTED]>
Changed-By: Martin Pitt <[EMAIL PROTECTED]>
Description: 
 cryptsetup - configures encrypted block devices
 cryptsetup-udeb - configures encrypted block devices
Launchpad-Bugs-Fixed: 151305
Changes: 
 cryptsetup (2:1.0.5-2ubuntu2) gutsy; urgency=low
 .
   * debian/initramfs/cryptroot-script:
     - If the supplied password worked, remove the prompt from usplash again,
       so that the user has some visual feedback that everything is alright.
       (LP: #151305)
     - Do not show the UUID device node of the outer physical device. It is
       scary ("/dev/disk/by-uuid/1234yadayada") and displaying it does not
       improve security at all: If attackers can tamper with your initramfs,
       they can also change the prompt, and if the UUID of the physical device
       changes, then booting will not even get that far. Now it is a much more
       friendly "Enter passphrase for sda5_crypt:" which is still technical,
       but it's necessary to point out which device will be unlocked in case
       there are several.
Files: 
 4644624875493272afb711c73ff26a97 1025 admin optional 
cryptsetup_1.0.5-2ubuntu2.dsc
 d613b33e0baddd7ec59e8c980400c161 47776 admin optional 
cryptsetup_1.0.5-2ubuntu2.diff.gz
Original-Maintainer: Debian Cryptsetup Team <[EMAIL PROTECTED]>
Package-Type: udeb
Vcs-Bzr: https://code.launchpad.net/~ubuntu-core-dev/cryptsetup/ubuntu

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

iD8DBQFHDmO/DecnbV4Fd/IRArM1AKDgSRbydWpak3oy9rx84TGdKKShWwCeJj2V
Uvh3LjWDSGMOmydofhDFi9U=
=fTmy
-----END PGP SIGNATURE-----



-- 
gutsy-changes mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/gutsy-changes

Reply via email to