FS#38533 - [libgcrypt] PBKDF2 very slow
Attached to Project:
Arch Linux
Opened by Olivier Brunel (jjacky) - Wednesday, 15 January 2014, 18:43 GMT
Last edited by Andreas Radke (AndyRTR) - Friday, 17 January 2014, 09:17 GMT
Opened by Olivier Brunel (jjacky) - Wednesday, 15 January 2014, 18:43 GMT
Last edited by Andreas Radke (AndyRTR) - Friday, 17 January 2014, 09:17 GMT
|
Details
Description:
PBKDF2 implementation in libgcrypt is very slow, this is easilly noticable e.g. when using cryptsetup to luksOpen using a keyfile, since it now (since libgcrypt 1.6.0 in recent update) uses it, instead of its own implementation as it used to before. Issue has been reported on cryptsetup[1], and a patch for libgcrypt[2] has actually already been accepted. Considering that luksOpenning a device with a keyfile can now take minutes where it used to be instant (also see [3]) it might be interesting to repackage with the patch. [1] http://code.google.com/p/cryptsetup/issues/detail?id=199 [2] http://lists.gnupg.org/pipermail/gcrypt-devel/2014-January/002865.html [3] https://bugzilla.redhat.com/show_bug.cgi?id=1051733 |
This task depends upon
Closed by Andreas Radke (AndyRTR)
Friday, 17 January 2014, 09:17 GMT
Reason for closing: Fixed
Additional comments about closing: 1.6.0-2, patch has been commited to 1.6 branch
Friday, 17 January 2014, 09:17 GMT
Reason for closing: Fixed
Additional comments about closing: 1.6.0-2, patch has been commited to 1.6 branch
and point to use abs for affected users.
See 1.6 branch: http://git.gnupg.org/cgi-bin/gitweb.cgi?p=libgcrypt.git;a=shortlog;h=refs/heads/LIBGCRYPT-1-6-BRANCH