Re: [dm-crypt] [ANNOUNCE] cryptsetup 1.1.1

From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] [ANNOUNCE] cryptsetup 1.1.1
Date: Sun, 23 May 2010 17:09:14 +0200	[thread overview]
Message-ID: <20100523150914.GA28011@tansi.org> (raw)
In-Reply-To: <4BF93B5B.3070907@redhat.com>

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

Compiles and seems to work. Thanks!

Arno

On Sun, May 23, 2010 at 04:27:39PM +0200, Milan Broz wrote:
> The stable cryptsetup 1.1.1 release is available at
> 
>    http://code.google.com/p/cryptsetup/
> 
> Feedback and bug reports are welcomed.
> 
> Milan
> mbroz@redhat.com
> 
> 
> Cryptsetup 1.1.1 Release Notes
> ==============================
> 
> Changes since version 1.1.1-rc2
> * Fix luksClose error if underlying device is LVM logical volume.
> 
> Changes since version 1.1.1-rc1
> * Fix automatic dm-crypt module loading.
> 
> Changes since version 1.1.0
> 
> Important changes:
> ~~~~~~~~~~~~~~~~~~
> 
> * Detects and use device-mapper udev support if available.
> 
>   This should allow synchronisation with udev rules and avoid races with udev.
> 
>   If package maintainer want to use old, direct libdevmapper device node creation,
>   use configure option --disable-udev.
> 
> * Supports device topology detection for data alignment.
> 
>   If kernel provides device topology ioctl calls, the LUKS data area
>   alignment is automatically set to optimal value.
> 
>   This means that stacked devices (like LUKS over MD/LVM)
>   should use the most optimal data alignment.
> 
>   (You can still overwrite this calculation using --align-payload option.)
> 
> * Prefers some device paths in status display.
>   (So status command will try to find top level device name, like /dev/sdb.)
> 
> * Fix package config file to use proper package version.
> 
> Other changes:
> ~~~~~~~~~~~~~~
> * Fix luksOpen reading of passphrase on stdin (if "-" keyfile specified).
> * Fix isLuks to initialise crypto backend (blkid instead is suggested anyway).
> * Properly initialise crypto backend in header backup/restore commands.
> * Do not verify unlocking passphrase in luksAddKey command.
> * Allow no hash specification in plain device constructor - user can provide volume key directly.
> * Try to use pkgconfig for device mapper library in configuration script.
> * Add some compatibility checks and disable LUKS suspend/resume if not supported.
> * Rearrange tests, "make check" now run all available test for package.
> * Avoid class C++ keyword in library header.
> 
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt
> 

- -- 
Arno Wagner, Dr. sc. techn., Dipl. Inform., CISSP -- Email: arno@wagner.name 
GnuPG:  ID: 1E25338F  FP: 0C30 5782 9D93 F785 E79C  0296 797F 6B50 1E25 338F
- ----
Cuddly UI's are the manifestation of wishful thinking. -- Dylan Evans

If it's in the news, don't worry about it.  The very definition of 
"news" is "something that hardly ever happens." -- Bruce Schneier 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iD8DBQFL+UUaGC7wC1BV+QYRAnk7AJ9tFggvKXDkmpCEhH3/CGTjZ6K04gCbBkpu
ZHmIBA+94jCtKwR22HPcfeE=
=HqZA
-----END PGP SIGNATURE-----