From: Milan Broz <gmazyland@gmail.com>
To: dm-crypt <dm-crypt@saout.de>
Cc: device-mapper development <dm-devel@redhat.com>
Subject: [dm-crypt] [ANNOUNCE] cryptsetup 1.4.2
Date: Thu, 12 Apr 2012 10:38:58 +0200 [thread overview]
Message-ID: <4F8694A2.2070804@gmail.com> (raw)
In-Reply-To: <4EA85582.3080904@redhat.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The stable cryptsetup 1.4.2 release is available at
http://code.google.com/p/cryptsetup/
Feedback and bug reports are welcomed.
Cryptsetup 1.4.2 Release Notes
==============================
Changes since version 1.4.1
* Add --keyfile-offset and --new-keyfile-offset parameters to API and CLI.
These options can be used to skip start of keyfile or device used as keyfile.
* Add repair command and crypt_repair() for known LUKS metadata problems repair.
Some well-known LUKS metadata corruptions are easy to repair, this
command should provide a way to fix these problems.
Always create binary backup of header device before running repair,
(only 4kB - visible header) for example by using dd:
dd if=/dev/<LUKS header device> of=repair_bck.img bs=1k count=4
Then you can try to run repair:
cryptsetup repair <device>
Note, not all problems are possible to repair and if keyslot or some header
parameters are overwritten, device is lost permanently.
* Fix header check to support old (cryptsetup 1.0.0) header alignment.
(Regression in 1.4.0)
* Allow to specify --align-payload only for luksFormat.
* Add --master-key-file option to luksOpen (open using volume key).
* Support UUID=<LUKS_UUID> format for device specification.
You can open device by UUID (only shortcut to /dev/disk/by-uuid/ symlinks).
* Support password verification with quiet flag if possible. (1.2.0)
Password verification can be still possible if input is terminal.
* Fix retry if entered passphrases (with verify option) do not match.
(It should retry if requested, not fail.)
* Fix use of empty keyfile.
* Fix error message for luksClose and detached LUKS header.
* Allow --header for status command to get full info with detached header.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iQIcBAEBAgAGBQJPhpShAAoJENmwV3vZPpj8vIoQAKmnjPd6x3s6nJjq0FRrFBZl
W+75LCImLInAZ4qOzGJys2m7rVBsrBPymcR59RDz/J6uY8QZh5gN7Fi4h59klOB5
Hi6JSsCl516z8c4fZ5m7qJA5FEX6Hn+PlpXaGzDqud+xjFz1Xd3sDC63GRMoUDlZ
N5HRbofC9PK+Cdq6joFwvPRvJCwp96cB2D7wR4b+bDy/Iau+Ydu0Ce+GcR99tyl5
kZ+umlQfgahYM0+wKnPYQZ3e9EKWS9h4746hnMLS0SmHEyczCx466tfm0DMxkRp3
hrx6LJ1goCIhuBwuYWMOahSMZNREjQ9HCCm2uBeHzIKBN1PtHm4vOTQ+VQWJ3ThI
WgMh7W7ezXGaJY8z2Xo1y5pNsspRin/kmsnogBvjd02CTyuda8ZDl2D2JpQcFbbO
JTz8vCAKJlZFB5NHoifhR8NAHsrcvc4aYUw4wu97hC+XzCkvrYXq3jrRCQ77yrYg
7CP3/MGyvWHPc5PbQVRBORO2R8UMKsPwcYqOuPzJFWlH7vxydvoXPa+5JXmlJTxZ
qW0Mf9ww8OioxqQat0uLI88Mgd2cA2Ys8Iv4Rp1TbAUvrTYjLS8qso+lkG7s7zcc
wmVaXz1WgyOwmjbsyV95qRKiCIA0NOqPUSNnKajmUjGuxBpHUjTQwsXPsMdbVXS/
c6+vm3SIWinLkje3bSbd
=QRJh
-----END PGP SIGNATURE-----
WARNING: multiple messages have this Message-ID (diff)
From: Milan Broz <gmazyland-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: dm-crypt <dm-crypt-4q3lyFh4P1g@public.gmane.org>
Cc: device-mapper development
<dm-devel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Subject: [ANNOUNCE] cryptsetup 1.4.2
Date: Thu, 12 Apr 2012 10:38:58 +0200 [thread overview]
Message-ID: <4F8694A2.2070804@gmail.com> (raw)
In-Reply-To: <4EA85582.3080904-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The stable cryptsetup 1.4.2 release is available at
http://code.google.com/p/cryptsetup/
Feedback and bug reports are welcomed.
Cryptsetup 1.4.2 Release Notes
==============================
Changes since version 1.4.1
* Add --keyfile-offset and --new-keyfile-offset parameters to API and CLI.
These options can be used to skip start of keyfile or device used as keyfile.
* Add repair command and crypt_repair() for known LUKS metadata problems repair.
Some well-known LUKS metadata corruptions are easy to repair, this
command should provide a way to fix these problems.
Always create binary backup of header device before running repair,
(only 4kB - visible header) for example by using dd:
dd if=/dev/<LUKS header device> of=repair_bck.img bs=1k count=4
Then you can try to run repair:
cryptsetup repair <device>
Note, not all problems are possible to repair and if keyslot or some header
parameters are overwritten, device is lost permanently.
* Fix header check to support old (cryptsetup 1.0.0) header alignment.
(Regression in 1.4.0)
* Allow to specify --align-payload only for luksFormat.
* Add --master-key-file option to luksOpen (open using volume key).
* Support UUID=<LUKS_UUID> format for device specification.
You can open device by UUID (only shortcut to /dev/disk/by-uuid/ symlinks).
* Support password verification with quiet flag if possible. (1.2.0)
Password verification can be still possible if input is terminal.
* Fix retry if entered passphrases (with verify option) do not match.
(It should retry if requested, not fail.)
* Fix use of empty keyfile.
* Fix error message for luksClose and detached LUKS header.
* Allow --header for status command to get full info with detached header.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iQIcBAEBAgAGBQJPhpShAAoJENmwV3vZPpj8vIoQAKmnjPd6x3s6nJjq0FRrFBZl
W+75LCImLInAZ4qOzGJys2m7rVBsrBPymcR59RDz/J6uY8QZh5gN7Fi4h59klOB5
Hi6JSsCl516z8c4fZ5m7qJA5FEX6Hn+PlpXaGzDqud+xjFz1Xd3sDC63GRMoUDlZ
N5HRbofC9PK+Cdq6joFwvPRvJCwp96cB2D7wR4b+bDy/Iau+Ydu0Ce+GcR99tyl5
kZ+umlQfgahYM0+wKnPYQZ3e9EKWS9h4746hnMLS0SmHEyczCx466tfm0DMxkRp3
hrx6LJ1goCIhuBwuYWMOahSMZNREjQ9HCCm2uBeHzIKBN1PtHm4vOTQ+VQWJ3ThI
WgMh7W7ezXGaJY8z2Xo1y5pNsspRin/kmsnogBvjd02CTyuda8ZDl2D2JpQcFbbO
JTz8vCAKJlZFB5NHoifhR8NAHsrcvc4aYUw4wu97hC+XzCkvrYXq3jrRCQ77yrYg
7CP3/MGyvWHPc5PbQVRBORO2R8UMKsPwcYqOuPzJFWlH7vxydvoXPa+5JXmlJTxZ
qW0Mf9ww8OioxqQat0uLI88Mgd2cA2Ys8Iv4Rp1TbAUvrTYjLS8qso+lkG7s7zcc
wmVaXz1WgyOwmjbsyV95qRKiCIA0NOqPUSNnKajmUjGuxBpHUjTQwsXPsMdbVXS/
c6+vm3SIWinLkje3bSbd
=QRJh
-----END PGP SIGNATURE-----
_______________________________________________
dm-crypt mailing list
dm-crypt-4q3lyFh4P1g@public.gmane.org
http://www.saout.de/mailman/listinfo/dm-crypt
next prev parent reply other threads:[~2012-04-12 8:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-26 18:46 [dm-crypt] [ANNOUNCE] cryptsetup 1.4.0 Milan Broz
2011-10-26 18:46 ` Milan Broz
2011-10-27 13:33 ` [dm-crypt] " Alexander Koch
2011-10-27 14:27 ` Christian Hesse
2011-10-28 13:49 ` Heinz Diehl
2011-11-09 12:46 ` [dm-crypt] [ANNOUNCE] cryptsetup 1.4.1 Milan Broz
2011-11-09 12:46 ` Milan Broz
2012-04-12 8:38 ` Milan Broz [this message]
2012-04-12 8:38 ` [ANNOUNCE] cryptsetup 1.4.2 Milan Broz
2012-05-31 8:38 ` [dm-crypt] [ANNOUNCE] cryptsetup 1.4.3 Milan Broz
2012-05-31 8:38 ` Milan Broz
2012-05-31 9:26 ` [dm-crypt] " Milan Broz
2012-05-31 9:26 ` Milan Broz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F8694A2.2070804@gmail.com \
--to=gmazyland@gmail.com \
--cc=dm-crypt@saout.de \
--cc=dm-devel@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.