From: Milan Broz <gmazyland@gmail.com>
To: dm-crypt <dm-crypt@saout.de>
Subject: [dm-crypt] [ANNOUNCE] cryptsetup 1.6.6
Date: Sat, 16 Aug 2014 12:49:30 +0200 [thread overview]
Message-ID: <53EF373A.4020700@gmail.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
The stable cryptsetup 1.6.6 release is available at
https://code.google.com/p/cryptsetup/
Please note that release packages are now located on kernel.org
https://www.kernel.org/pub/linux/utils/cryptsetup/v1.6/
Feedback and bug reports are welcomed.
Cryptsetup 1.6.6 Release Notes
==============================
Changes since version 1.6.5
* LUKS: Fix keyslot device access for devices which
do not support direct IO operations. (Regression in 1.6.5.)
* LUKS: Fallback to old temporary keyslot device mapping method
if hash (for ESSIV) is not supported by userspace crypto
library. (Regression in 1.6.5.)
* Properly activate device with discard (TRIM for SSDs)
if requested even if dm_crypt module is not yet loaded.
Only if discard is not supported by the old kernel then
the discard option is ignored.
* Fix some static analysis build warnings (scan-build).
* Report crypto lib version only once (and always add kernel
version) in debug output.
Cryptsetup API NOTE:
The direct terminal handling for passphrase entry will be removed from
libcryptsetup in next major version (application should handle it itself).
It means that you have to always either provide password in buffer or set
your own password callback function through crypt_set_password_callback().
See API documentation (or libcryptsetup.h) for more info.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBCAAGBQJT7zcvAAoJENmwV3vZPpj8+/wQAKJ6pynllNWEsIJr0cUlibui
Ta2VZwpI9t1Dked/vmuB2Z2PoLqTQ7ykuH3JFR9nJogBXXMH/iJWGhWlEOY3AcMz
LwPTu2dE4Wa2SUdYFvtjX6BnjcxVCFZ2O02ZMDyY0N/uv6CBs+vKXbu8vCnP/LOo
6aXqU8X82AceRiK4MEvE5tSM+H6kO6idRtchFmh4pJg/W3YjFHKkIoMAxmDepiIT
1t4ALHrUKhNDLJv6b2xvRySvsd3pMHHBpYRIM5l/8+p87k/ngDNVYPeTBJhlVSZO
Q8NHPaK2lQO9aD1IazPvw9ibpBwdg0mHcfDJcPDGpum1CXy+svECh0ySK+dkNfvH
204jgD9D7IrADWnToOThmYPLkAmwIqTytniw9kl4eKYjimC/TzjeO83dmhB24Hhe
PEuFUc8xx7/8f/XJkB+oSeD/FXZGU9/nAaGOkirsiF69p85i6llRE6ADc0iDUzUD
08Wywl+9jZfbNh6w4i53EId8pZIj5NvlbikdDy/LMiZiw2s98tfXtw1x02d/2k6H
JvTWyz0L1B88ieS/jumdCwHnVRdIxh6G1Ls2SxneKIgsFpU6dhKtEiNZSpZA30fn
wc58TPU6JelAw85wV8qXXS/Ws4RNb17Vwh0Y8KO+eM2gVhGHqhrgEJ3S1iQ37rqK
y39R6EFlS4HqBymC72rF
=cXwx
-----END PGP SIGNATURE-----
next reply other threads:[~2014-08-16 10:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-16 10:49 Milan Broz [this message]
2014-08-16 10:59 ` [dm-crypt] [ANNOUNCE] cryptsetup 1.6.6 .. ink ..
2014-08-16 11:56 ` Milan Broz
2014-08-16 11:25 ` Arno Wagner
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=53EF373A.4020700@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.