From: Milan Broz <gmazyland@gmail.com>
To: dm-crypt <dm-crypt@saout.de>
Subject: [dm-crypt] [ANNOUNCE] cryptsetup 1.7.1
Date: Sun, 28 Feb 2016 14:54:30 +0100 [thread overview]
Message-ID: <56D2FC16.3070306@gmail.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
The stable cryptsetup 1.7.1 release is available at
https://gitlab.com/cryptsetup/cryptsetup
Please note that release packages are located on kernel.org
https://www.kernel.org/pub/linux/utils/cryptsetup/v1.7/
Feedback and bug reports are welcomed.
Cryptsetup 1.7.1 Release Notes
==============================
Changes since version 1.7.0
* Code now uses kernel crypto API backend according to new
changes introduced in mainline kernel
While mainline kernel should contain backward compatible
changes, some stable series kernels do not contain fully
backported compatibility patches.
Without these patches most of cryptsetup operations
(like unlocking device) fail.
This change in cryptsetup ensures that all operations using
kernel crypto API works even on these kernels.
* The cryptsetup-reencrypt utility now properly detects removal
of underlying link to block device and does not remove
ongoing re-encryption log.
This allows proper recovery (resume) of reencrypt operation later.
NOTE: Never use /dev/disk/by-uuid/ path for reencryption utility,
this link disappears once the device metadata is temporarily
removed from device.
* Cryptsetup now allows special "-" (standard input) keyfile handling
even for TCRYPT (TrueCrypt and VeraCrypt compatible) devices.
* Cryptsetup now fails if there are more keyfiles specified
for non-TCRYPT device.
* The luksKillSlot command now does not suppress provided password
in batch mode (if password is wrong slot is not destroyed).
Note that not providing password in batch mode means that keyslot
is destroyed unconditionally.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCAAGBQJW0vwWAAoJENmwV3vZPpj8QaUP/0VNGxqjXD2cobW/Jx81bvl3
oRxIa0unknO+hLjmSnEmAzNf0k5NMhjViYzKYOZXMeS5k/IK1sPCCWlZtWqBpGH2
zI+avWBH9TK18w2XFbx7KvccORi/A9pmNlUqNzciHybQZMRJq7JjHb6g3HCeoJuu
cbP/wd5fTzCw+f/EuwN4S9xMvYENF+vN1dtoqtIvjsv9AxuFxGasU2FIlwRAJG5x
o6ZaY5d7DSrpr7y7G9t1AeSmRK30ZeoDfHQG4a5bUXAjxb52zCWc+7/mHGYM7ifS
W8VPH4/h9azle/02Gk1mWFW5YphSA89xBLZV8GQ7fWPdHe5W6Lyv74X8mXZju66b
feQK7SOTNRhHPx4xy43MiveQ1z5e2/Z7A3F3QEKOciofR7QJjmhz8FqLTHB4ehum
/PrnrSj9w+iT+584hHpEYns89noaX/1erSizRJfgaJQ3+4CPFVohYb7dPYfuS710
T2+l7AT5hliLsHMrnRQootUtZqy7Jl5AHklZ69KNupJYk1s/xoakxVBFCaohMWW2
v4Cn9rrC0x8cLTSn5YT+RnPyenstmum3ZSEN8ugXcZxZv2HcxLCmU+ipuYHX81MT
ME8nBnkf+5qCnm+Hul8dS8nNQrkd92KGQff5m1c6AEnolg7BPWDdgCFADemr4xiG
IKJdOz3Nnf9OMZVI/dM6
=Rkqt
-----END PGP SIGNATURE-----
reply other threads:[~2016-02-28 13:54 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=56D2FC16.3070306@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