-
cryptsetup (2:1.0.5-2ubuntu12) hardy; urgency=low
* added debian/patches/07_typos_fix.dpatch: fixed typos in man pages. (LP: #164181)
-- Bruno Barrera Yever <email address hidden> Mon, 07 Apr 2008 18:43:05 -0500
-
cryptsetup (2:1.0.5-2ubuntu11) hardy; urgency=low
* debian/initramfs/cryptroot-script: Do show the disk name after all, since
some people use multiple encrypted partitions as LVM PVs. (LP: #201413)
-- Martin Pitt <email address hidden> Sun, 06 Apr 2008 11:54:41 -0600
-
cryptsetup (2:1.0.5-2ubuntu10) hardy; urgency=low
* debian/initramfs/cryptroot-script: Do not mention the name of the
encrypted device. It is just technobabble anyway (sda4_crypt), and there
is just one root partition ever, so it is not needed to tell apart
different partitions. From a security POV, someone who can change your
initramfs to boot a different root partition can just as well change the
strings, too. (LP: #201413)
-- Martin Pitt <email address hidden> Wed, 02 Apr 2008 15:51:53 +0200
-
cryptsetup (2:1.0.5-2ubuntu9) hardy; urgency=low
* debian/scripts/luksformat: Use 256 bit key size by default.
(LP: #78508)
* debian/patches/02_manpage.dpatch: Clarify default key sizes (128 for
luksFormat and 256 for create) in cryptsetup.8. (side-note in LP #78508)
-- Martin Pitt <email address hidden> Wed, 27 Feb 2008 17:43:46 +0100
-
cryptsetup (2:1.0.5-2ubuntu8) hardy; urgency=low
* Fix -x calls and access() call.
-- Scott James Remnant <email address hidden> Fri, 14 Dec 2007 16:54:53 +0000
-
cryptsetup (2:1.0.5-2ubuntu7) hardy; urgency=low
* debian/initramfs/cryptroot-script: call udevadm instead of udevsettle
* debian/patches/06_call_udevsettle.dpatch: likewise
-- Scott James Remnant <email address hidden> Fri, 14 Dec 2007 16:11:36 +0000
-
cryptsetup (2:1.0.5-2ubuntu6) hardy; urgency=low
* Make cryptsetup understand devices specified by UUID=... or LABEL=
in crypttab. (LP: #153597)
-- Andrea Colangelo <email address hidden> Mon, 29 Oct 2007 18:22:51 +0100
-
cryptsetup (2:1.0.5-2ubuntu5) hardy; urgency=low
* reenable additional udevsettle calls in cryptroot hook from
https://launchpad.net/bugs/85640, LP: #132373.
* change maintainer to ubuntu-core-dev.
* use Vcs-Bzr instead of XSCB-Vcs-Bzr header in debian/control.
-- Reinhard Tartler <email address hidden> Thu, 08 Nov 2007 23:52:19 +0100
-
cryptsetup (2:1.0.5-2ubuntu4) hardy; urgency=low
* reapply changes from version 2:1.0.5-2ubuntu2, got dropped with last
upload. Sorry, pitti.
* convert patch to lib/libdevmapper.c to a dpatch.
-- Reinhard Tartler <email address hidden> Sun, 04 Nov 2007 21:42:43 +0100
-
cryptsetup (2:1.0.5-2ubuntu3) hardy; urgency=low
* RELIABILY FIX: lib/libdevmapper.c: Ensure that pending device creation
events are being processed by calling /sbin/udevsettle. Patch based on
OpenSUSE bug #285478, LP: #132373.
* Based on the change above, the patch from LP #85640 is no longer needed.
dropping the relevant parts.
* Fix debian/rules to not fail to build if autom4te.cache is left behind
from a previous incomplete build.
-- Reinhard Tartler <email address hidden> Fri, 02 Nov 2007 20:53:31 +0100
-
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.
-- Martin Pitt <email address hidden> Thu, 11 Oct 2007 19:51:58 +0200
