Ayoub Chouak

> Do we have any tests covering this? `test/recipes/20-test_enc.t` seems like it.

> We will need a CLA submitted to be able to accept this PR, could you please follow the instructions at: > https://www.openssl.org/policies/cla.html I will shortly submit the CLA as...

> We will need a CLA submitted to be able to accept this PR, could you please follow the instructions at: > https://www.openssl.org/policies/cla.html I have submitted the CLA.

I'm wondering whether it would be at all possible to expose the error stack to FIPS provider code? This would enable us to use the `err_clear_last_constant_time` trick to optionally raise...

> probably something similar to this function? > > ``` > crypto/provider_core.c: { OSSL_FUNC_CORE_CLEAR_LAST_ERROR_MARK, > include/openssl/core_dispatch.h:# define OSSL_FUNC_CORE_CLEAR_LAST_ERROR_MARK 9 > providers/fips/fipsprov.c: case OSSL_FUNC_CORE_CLEAR_LAST_ERROR_MARK: > ``` > > just, that the...

> additionally you would need to do this: > > ``` > --- a/util/libcrypto.num > +++ b/util/libcrypto.num > @@ -5423,3 +5423,4 @@ ASN1_item_d2i_fp_ex ? 3_0_0 EXIST::FUNCTION:STDIO > ASN1_item_d2i_bio_ex ? 3_0_0...

Can anyone trigger the workflows?

I have committed the changes to fix the failing `check_docs` check but it's still not generating the documentation for some reason. I also can't understand what's the issue with `check_update`...

Can anyone some light on why the documentation is not being generated even though the .pod file is clearly in the correct directory? Apparently `check_docs` is failing because of that....

> > Can anyone some light on why the documentation is not being generated even though the .pod file is clearly in the correct directory? Apparently `check_docs` is failing because...