From: Milan Broz <gmazyland@gmail.com>
To: dm-crypt <dm-crypt@saout.de>
Subject: [dm-crypt] [ANNOUNCE] cryptsetup 1.5.1
Date: Tue, 16 Oct 2012 22:26:43 +0200 [thread overview]
Message-ID: <507DC303.2090009@gmail.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The stable cryptsetup 1.5.1 release is available at
http://code.google.com/p/cryptsetup/
Feedback and bug reports are welcomed.
Cryptsetup 1.5.1 Release Notes
==============================
Changes since version 1.5.0
* The libcryptsetup library now tries to initialize device-mapper backend and
loop devices only if they are really needed (lazy initializations).
This allows some operations to be run by a non-root user.
(Unfortunately LUKS header keyslot operations still require temporary dm-crypt
device and device-mapper subsystem is available only to superuser.)
Also clear error messages are provided if running as non-root user and
operation requires privileged user.
* Veritysetup can be now used by a normal user for creating hash image to file
and also it can create hash image if doesn't exist.
(Previously it required pre-allocated space.)
* Added crypt_keyslot_area() API call which allows external tools
to get exact keyslot offsets and analyse content.
An example of a tool that searches the keyslot area of a LUKS container
for positions where entropy is low and hence there is a high probability
of damage is in misc/kesylot_checker.
(Thanks to Arno Wagner for the code.)
* Optimized seek to keyfile-offset if key offset is large.
* Fixed luksHeaderBackup for very old v1.0 unaligned LUKS headers.
* Various fixes for problems found by several static analysis tools.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iQIcBAEBAgAGBQJQfcL4AAoJENmwV3vZPpj8NBcQAMlRbn7ijeGlyNIwrfqhqPg1
a/09d8MVJkriZQ3Gk/BUYA4WhBSSOTV5TilKkJS4yAK48bjsZ1o27IObJ+sJR5U+
A9zw+nL+2owqoXfITndYLdJr6/h07PBDksRT6SzQTW9O47853CKZDrQUU3cF1MgW
hmJ99pD5ZLCSQsPXPtePpa/mAWC6X3fVoxLysI0F72Ww0l7o/3HAktZy8BjYA/sh
ZrIP9kqvai1lfCckzdSkMrtVNFV5glWdH7fh+RDNQHIYOUCwS0rC/iBQsWA3UwZz
6s2CzhKDJ2AWf3wf13uT8iMpMDfNrbaxh2imUYJtpHvn4fqmmu+7j31cPwIjHJ49
pSXek488WjSKcbDOr9WXE7O5JZe7BrwzsT/T1APSOEIq7SqEhprQYztWwTLBAsWL
IJP/3wEDw5c5zA3ldpc+9jF6wScfBtumOWffWVHWSnY0J/R6e+BSwxubnnCJRaUI
4ZOE+AYQXzTqB37a5Jzkh1PljzJkHNsPGswsUFNEpCCxGNQULCD/rLbPobcSeSX4
qN78Ld7kxBcEnDAQO3fyssL3pjDHHB1tNiiGKiqtXGXKEgM+qWxob7Esa3fgC1oL
JmaC7v9BKalcOfGbfo41x/xwbJyCVgExMyOipnD6OGzeR6AE9GHH77ntZ9HF9Rc0
4FzWzUHVC3uwl1dRAnXH
=PwyS
-----END PGP SIGNATURE-----
reply other threads:[~2012-10-16 20:26 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=507DC303.2090009@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.