dm-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Milan Broz <mbroz-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: dm-crypt <dm-crypt-4q3lyFh4P1g@public.gmane.org>
Cc: device-mapper development
	<dm-devel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Subject: [ANNOUNCE] cryptsetup 1.4.1
Date: Wed, 09 Nov 2011 13:46:15 +0100	[thread overview]
Message-ID: <4EBA7617.4030401@redhat.com> (raw)
In-Reply-To: <4EA85582.3080904-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

The stable cryptsetup 1.4.1 release is available at

   http://code.google.com/p/cryptsetup/

Feedback and bug reports are welcomed.


Cryptsetup 1.4.1 Release Notes
==============================

Changes since version 1.4.0

* Merge experimental Python cryptsetup (pycryptsetup) binding.

  This option is disabled by default, you can enable build of Python binding
  with --enable--python configure switch.

  Note that binding currently covers only partial libcryptsetup functions,
  mainly LUKS device handling needed for Anaconda installer.
  Until now provided separately as python-cryptsetup.
  Thanks to Martin Sivak for the code.

  See python subdirectory for more info.

  Python binding code is experimental for now, no stable API guarantee.

* Fix crypt_get_volume_key_size() for plain device.
  (cryptsetup status reported zero key size for plain crypt devices).

* Fix typo in set_iteration_time API call (old name remains for compatibility reasons).

* Fix FSF address in license and add LGPL license text.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAk66dhcACgkQf1Jlc7shgi8RCgCfXkzU1oUSDpsEiSxHQ/rd51l1
uuEAn3zxefcqXz7JiW3hjW4GlEnAl1gj
=ePPt
-----END PGP SIGNATURE-----
_______________________________________________
dm-crypt mailing list
dm-crypt-4q3lyFh4P1g@public.gmane.org
http://www.saout.de/mailman/listinfo/dm-crypt

  parent reply	other threads:[~2011-11-09 12:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-26 18:46 [ANNOUNCE] cryptsetup 1.4.0 Milan Broz
     [not found] ` <4EA85582.3080904-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2011-11-09 12:46   ` Milan Broz [this message]
2012-04-12  8:38   ` [ANNOUNCE] cryptsetup 1.4.2 Milan Broz
2012-05-31  8:38   ` [ANNOUNCE] cryptsetup 1.4.3 Milan Broz
     [not found]     ` <4FC72DF2.9070106-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-05-31  9:26       ` Milan Broz

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=4EBA7617.4030401@redhat.com \
    --to=mbroz-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=dm-crypt-4q3lyFh4P1g@public.gmane.org \
    --cc=dm-devel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    /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;
as well as URLs for NNTP newsgroup(s).