On 29/10/2021 16:40, Cristian Andrei Sandu wrote:
Hi all,
I’m currently updating an application from OpenSSL 1.0.2d to OpenSSL
3.0.0 in preparation for a FIPS 140-2 submission and I’m not sure how to
approach the issue of induced failures for the power on self tests.
In OpenSSL 1.0.2d we
Hi all,
I'm currently updating an application from OpenSSL 1.0.2d to OpenSSL 3.0.0 in
preparation for a FIPS 140-2 submission and I'm not sure how to approach the
issue of induced failures for the power on self tests.
In OpenSSL 1.0.2d we used to use FIPS_post_set_callback() for this purpose, b
Hi Alex,
On 29/10/2021 14:32, Alex Dankow wrote:
Hi OpenSSL team!
I wrote a provider for Windows certificates and implemented "openssl ca".
Now, I think it would be fun to see a HTTPS server using certificates
installed in Windows storage.
Nice!
Certificate is loaded using load_cert_pass (
On 28/10/2021 22:46, Kory Hamzeh wrote:
Hi Matt,
I am making the changes that you suggested, I think I can get the X and Y by
using
EVP_PKEY_get_bn_param() with OSSL_PKEY_PARAM_EC_PUB_X and _PUB_Y.
Yes. Correct.
What I cannot figure out is how to get R and S. If I had an ECDSA_SIG, I w
Hi OpenSSL team!
I wrote a provider for Windows certificates and implemented "openssl ca".
Now, I think it would be fun to see a HTTPS server using certificates
installed in Windows storage.
Certificate is loaded using load_cert_pass (taken from apps.c) with custom
uri "wincert://11:22:33",
OpenSSL 1.1.1l does not contain -D_XOPEN_SOURCE=700.
So you must have added it on the Configure command line or by patching the source code.
On AIX (any version), this disables _ALL_SOURCE.