- User Since
- Mar 27 2017, 4:48 PM (225 w, 5 d)
Wed, Jul 7
That crcalgo can be any digest algorithm and SHA256 seems best option to me.
Tue, Jul 6
Fri, Jul 2
Thu, Jul 1
Wed, Jun 30
Thanks a lot.
Mon, Jun 28
P192, P224, P256 and P384 are affected.
Attached patch should fix the issue:
Thanks for reporting. There is two commits in that commit range, including https://dev.gnupg.org/rC9d909cb67e70fd792926ac1e2ab305b2cc96bc27 which adds fast reduction for NIST curves. So obviously something is wrong there. Is secp192r1 only curve that is giving wrong results?
Jun 24 2021
Jun 19 2021
Jun 3 2021
May 17 2021
Apr 28 2021
Apr 26 2021
Apr 12 2021
Apr 6 2021
Note that rndjent.c is already build with -O0 as can be seen in example above. That warning could be silenced by surrounding pragma with #ifdef __OPTIMIZE__ (with should be supported by GCC and Clang).
Apr 1 2021
Mar 30 2021
@werner Can you comment about bugfix release?
These functions are internal to library and, for example, on linux/windows builds are not externally available.
Mar 29 2021
This patch should work if configure properly detects need for extra underscore on C symbols:
Mar 26 2021
Mar 25 2021
Thanks for the report.
Mar 12 2021
Mar 9 2021
Pushed to master with two commits:
Mar 7 2021
I posted patch-set to mailing-list. Please check if AUTHORS/LICENSES updates are ok.
I've cleaned up the patch from D501 and tweaked the implementation a bit for performance. Here's patches attached:
Mar 6 2021
Fixed typos and applied to master. Thanks.
Mar 3 2021
Feb 12 2021
Feb 6 2021
Problem with clang and these files was resolved by replacement of assembler macros with C preprocessor macros.
Feb 4 2021
The 'what != NULL' case is handled by the "Strip trailing LF" part at the end of function. These data strings always end with '\n', so null-termination gets done there.
Feb 3 2021
Jan 31 2021
Does it build if configure with parameter 'ac_cv_sys_symbol_underscore=yes'? <path-to-libgcrypt-source>/configure ac_cv_sys_symbol_underscore=yes --host=aarch64-apple-darwin ...
Jan 29 2021
Thanks for your report.
Jan 28 2021
Patch for this bug is available here, "attachment-0001.bin": https://lists.gnupg.org/pipermail/gcrypt-devel/2021-January/005079.html
I tested xenial with gcc-5.3 (xenial distro repo) and gcc-5.4 (xenial-updates distro repo) and libgcrypt 1.9.0 from git repo and from tarball. I did not get any errors.