From: "Thomas Bächler" <thomas@archlinux.org>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] [ANNOUNCE] cryptsetup 1.6.4
Date: Thu, 27 Feb 2014 18:30:44 +0100 [thread overview]
Message-ID: <530F7644.4040003@archlinux.org> (raw)
In-Reply-To: <530F4E30.6000204@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 932 bytes --]
Am 27.02.2014 15:39, schrieb Milan Broz:
> The stable cryptsetup 1.6.4 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.
Thank you for your work on cryptsetup.
> * Add internal "whirlpool_gcryptbug hash" for accessing flawed
> Whirlpool hash in gcrypt (requires gcrypt 1.6.1 or above).
>
> The gcrypt version of Whirlpool hash algorithm was flawed in some
> situations.
>
> This means that if you used Whirlpool in LUKS header and upgraded
> to new gcrypt library your LUKS container become inaccessible.
>
> Please refer to cryptsetup FAQ for detail how to fix this situation.
I don't see any information on how to fix this problem in the FAQ. Can
you provide a more precise reference?
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]
next prev parent reply other threads:[~2014-02-27 17:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-27 14:39 [dm-crypt] [ANNOUNCE] cryptsetup 1.6.4 Milan Broz
2014-02-27 17:30 ` Thomas Bächler [this message]
2014-02-28 7:51 ` Milan Broz
2014-02-28 11:29 ` Milan Broz
2014-02-28 11:38 ` Arno Wagner
2014-02-28 21:26 ` Sven Eschenberg
2014-02-28 21:46 ` Arno Wagner
2014-02-28 22:06 ` Sven Eschenberg
2014-02-28 23:27 ` Arno Wagner
2014-03-01 7:39 ` Sven Eschenberg
2014-03-01 8:35 ` Milan Broz
2014-03-01 11:32 ` Sven Eschenberg
2014-03-01 16:50 ` Heinz Diehl
2014-03-01 19:44 ` Arno Wagner
2014-03-02 7:35 ` Heinz Diehl
2014-03-02 15:17 ` Arno Wagner
2014-03-01 13:50 ` Arno Wagner
2014-02-27 21:44 ` Heinz Diehl
2014-02-27 22:36 ` 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=530F7644.4040003@archlinux.org \
--to=thomas@archlinux.org \
--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