- User Since
- Mar 27 2017, 4:48 PM (157 w, 4 d)
Feb 3 2020
Feb 2 2020
Feb 1 2020
Thanks for reporting this this. Your patch is correct.
Jan 22 2020
Patch have been applied to master, https://git.gnupg.org/cgi-bin/gitweb.cgi?p=libgcrypt.git;a=commit;h=79ed620ec46adbb08f5cea6a4865a95a436e4109
Jan 19 2020
Thanks for bug fix. I've prepared patch and send it to mailing list https://lists.gnupg.org/pipermail/gcrypt-devel/2020-January/004885.html. Let me know if Reported-by is ok/enough. I would have liked to put you as author of commit, but this Differential interface of quite horrible and does not give all the needed information (mainly "name <email>" format for git).
Dec 25 2019
Dec 9 2019
I've been wondering this also. I can start working on this.
Nov 28 2019
Nov 21 2019
Nov 8 2019
Please note that C-based intrinsic implementation is the way to go now as that is the path chosen for PowerPC implementations in libgcrypt.
Nov 5 2019
Oct 16 2019
Sep 26 2019
Sep 16 2019
Sep 15 2019
Sep 6 2019
Poly1305 addition helper for ppc64 posted on mailing list: https://lists.gnupg.org/pipermail/gcrypt-devel/2019-September/004804.html
Sep 3 2019
PowerPC SHA-256 and SHA-512 implementations with little bit more tuning committed. Most notably, SHA-512 on POWER8 now gives similar performance to OpenSSL:
Aug 31 2019
Aug 26 2019
Aug 25 2019
I'll start working on PowerPC GHASH implementation in September after SHA2 is done.
I'll start working on new PowerPC SHA2 implementations for libgcrypt in coming weeks.
Patches for PowerPC AES acceleration sent to mailing-list, based partly on initial work by Shawn Landden (@slandden): https://lists.gnupg.org/pipermail/gcrypt-devel/2019-August/004788.html
Jul 18 2019
Jul 8 2019
Thanks. I really like this Altivec intrinsic approach. I might reimplement rest of the bulk block cipher functions this way later (if I ever get PPC HW access).