From: Milan Broz <gmazyland@gmail.com>
To: dm-crypt <dm-crypt@saout.de>
Subject: [dm-crypt] [ANNOUNCE] cryptsetup 1.6.1
Date: Sun, 31 Mar 2013 17:00:17 +0200 [thread overview]
Message-ID: <51584F81.1010105@gmail.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
The stable cryptsetup 1.6.1 release is available at
http://code.google.com/p/cryptsetup/
Feedback and bug reports are welcomed.
Cryptsetup 1.6.1 Release Notes
==============================
Changes since version 1.6.0
* Fix loop-AES keyfile parsing.
Loop-AES keyfile should be text keyfile, reject keyfiles which
are not properly terminated.
* Fix passphrase pool overflow for too long TCRYPT passphrase.
(Maximal TCRYPT passphrase length is 64 characters.)
* Return EPERM (translated to exit code 2) for too long TCRYPT passphrase.
* Fix deactivation of device when failed underlying node disappeared.
* Fix API deactivate call for TCRYPT format and NULL context parameter.
* Improve keyslot checker example documentation.
* Report error message if deactivation fails and device is still busy.
* Make passphrase prompts more consistent (and remove "LUKS" form prompt).
* Fix some missing headers (compilation failed with alternative libc).
* Remove non-functional API UUID support for plain and loopaes devices.
(For not persistent activation UUID.)
* Properly cleanup devices on interrupt in api-test.
* Support all tests run if kernel is in FIPS mode.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iQIcBAEBCAAGBQJRWE94AAoJENmwV3vZPpj8yAsQAJ1Mb4CCk5Ty+Xrp6dHh8rtF
laKXpRi8mCivxq7qVFt+Dv+Te1kfUL2kam3gYXgdK3HlQ8Xb+LMjzaUlO0c8+Mvn
E123OlB1xhjNp/3bSo54MOodw18nA1Ax9aslrCpgewEyxS+4MzC97Tnw35TeFd0Q
NENT4Zhcu5My2Ws9+LJCHjjm7tYFVoJKQVZjeycsIE3mvqTBcr7mr5emscKzfcj6
+gEbOC2d1gOK8vzW+Sjj0hKJEPs9O5bG04xqX+ANgJhbx4x6LB62Btv60+V8lDBD
5eQJJ2nxEGgCsGsvgu4MUyW8xg6q8KU2xpuwF3OPJ4OZMB/2cn1IV+3eS/PBfrkj
rqx91Iwqkuubx+1vgzTffLLwEfpGoR434Z5/NINSOrYwwS1IyeFX6/t/2+4QsNrt
B6yLmhLSJ1/eOZCCyaTYlzIlMUBTBREHF/RKbeFs6SFUs6sTDx2lsdIwHc/aDyPS
KOlniTO8r0CxNScfuap3US3XYbLNqCyukeD0xgSGFOiTYCVciDzHbR4T+go7mH0/
c8bCBCa1e0CyzKVXuNU83phXEQIHF6AKr2fh/sm4Q9vK5Myo4mekv+de7n/9iASr
wVI+sJVFqucfmQqCdW/B/jj7dilYRLV8bbsF4eIu/8nUPGvHuAeqiumwN88HgOFL
ynmFjMA7o6e7MVZMGFK6
=rjcF
-----END PGP SIGNATURE-----
reply other threads:[~2013-03-31 15:00 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=51584F81.1010105@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 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.