From: Milan Broz <gmazyland@gmail.com>
To: dm-crypt <dm-crypt@saout.de>
Subject: [dm-crypt] [ANNOUNCE] cryptsetup 1.6.2
Date: Sun, 04 Aug 2013 19:51:29 +0200 [thread overview]
Message-ID: <51FE94A1.9060009@gmail.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
The stable cryptsetup 1.6.2 release is available at
http://code.google.com/p/cryptsetup/
Feedback and bug reports are welcomed.
Cryptsetup 1.6.2 Release Notes
==============================
Changes since version 1.6.1
* Print error and fail if more device arguments are present for isLuks command.
* Fix cipher specification string parsing (found by gcc -fsanitize=address option).
* Try to map TCRYPT system encryption through partition
(allows to activate mapping when other partition on the same device is mounted).
* Print a warning if system encryption is used and device is a partition.
(TCRYPT system encryption uses whole device argument.)
* Disallow explicit small payload offset for LUKS detached header.
LUKS detached header only allows data payload 0 (whole data device is used)
or explicit offset larger than header + keyslots size.
* Fix boundary condition for verity device that caused failure for certain device sizes.
* Various fixes to documentation, including update FAQ, default modes
and TCRYPT description.
* Workaround for some recent changes in automake (serial-tests).
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)
iQIcBAEBCAAGBQJR/pSZAAoJENmwV3vZPpj8CV8P/2cXHZ6kkmtrTJ5XTQEuBi4X
GQtRPzh+wzpuCqWcx87StVnt+44OwwUu5CKaMUoXd4vfRWLRURvGqjZcwIcmGBM1
PnVDkcdbc5gNzg8PDLtqqC3hROwQMNYMhnpuFbp0zBKtbamAMF0xfxecZSrb8lC0
4oeYe6Ue9NwKXdMJe1h11eqKWuMoLineMaE6qD0OlUB4Xo057o13tUk48po0WW5v
ehlBkAIIzjbFyiRZzoMI7k/venD54Gp6AywEESh7WCrb1y6FeI7WDjBouzWbNQcx
RXSJbwAJg2UGvcVEjiJ3UwotIzIj8kmBKrfoF1dew45eh9Z4bFPwzFfV3+y+/Fnt
uFBQoJS2DB/0opUmai1yla4TRwE6sFaKaXsAFPfrk+Kdmjz/2qGcoJviwkLQTwTH
ha4gCiVrDa09yBQ1Hhum48oJJHZUpIDuAVs35lSF13B5omc4DnP8gwpGZojO6xOx
EiLKUOejzV78L9b4N0NnY2F1abvhKTQ3+ifS+63oxawG0huysgI3iJAjkLxsPjpp
WZYjpaKDKUY0eJAz2D4a/ihPGq9GZKm7Tb8i2wcMjnsdhsZfBhow3VoeQ21rW80L
duDIrqSPGOsbPsGgB49kmR1nI/QbJVjDJTTNG6tfMA9LDOe5m5nOx+KVaBnw9e1l
2sT6/wHb56aqH3N0Xzi8
=CTkP
-----END PGP SIGNATURE-----
reply other threads:[~2013-08-04 17:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=51FE94A1.9060009@gmail.com \
--to=gmazyland@gmail.com \
--cc=dm-crypt@saout.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox