Pull Request (patch libgcrypt)

Werner Koch wk at gnupg.org
Fri Aug 21 10:27:14 CEST 2020

On Thu, 20 Aug 2020 19:57, Antonio Harres said:

> The key point here is that the relevant portion of code is using fopen to
> probe for the existence of the file, this may return all sorts of errors,
> but commonly it's ENOENT. which is then returned into any code that is
> initializing libgcrypt. But, I'm getting errno at something that is not an

Sorry, that is not correct.  Here is the function's prototype:

  void _gcry_initialize_fips_mode (int force)

as you can see that function _cannot_ return any error code.  I already
explained that you can't assume that an arbitrary library like Libgcrypt
makes any guarantee not to change the ERRNO of the thread.  In fact
there is no guarantee for that for many libc function's either.



Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: <https://lists.gnupg.org/pipermail/gcrypt-devel/attachments/20200821/e60a8d4a/attachment.sig>

More information about the Gcrypt-devel mailing list