Matt Caswell wrote:
> Please see my blog post for an OpenSSL 3.0 and FIPS Update:
> https://www.openssl.org/blog/blog/2019/02/13/FIPS-update/
Thank you, it is very useful to have these plans made up front.
I think your posts should probably explain what happened to 2.x, and if this
On 13/02/2019 17:32, Jakob Bohm via openssl-users wrote:
> On 13/02/2019 12:26, Matt Caswell wrote:
>> Please see my blog post for an OpenSSL 3.0 and FIPS Update:
>>
>> https://www.openssl.org/blog/blog/2019/02/13/FIPS-update/
>>
>> Matt
>
> Given this announcement, a few questions arise:
>
>
On 13/02/2019 12:26, Matt Caswell wrote:
Please see my blog post for an OpenSSL 3.0 and FIPS Update:
https://www.openssl.org/blog/blog/2019/02/13/FIPS-update/
Matt
Given this announcement, a few questions arise:
- How will a FIPS provider in the main tarball ensure compliance
with the
On 13/02/2019 14:00, Jason Schultz wrote:
> Thanks for your response. A follow up question based on Matt Caswell's blog
> post: Does the blog post imply that the next FIPS module will be based on
> OpenSSL 3.0? Or is 3.0 a longer term thing and the next FIPS module will be
> for
> OpenSSL
Thanks for your response. A follow up question based on Matt Caswell's blog
post: Does the blog post imply that the next FIPS module will be based on
OpenSSL 3.0? Or is 3.0 a longer term thing and the next FIPS module will be for
OpenSSL 1.1.1?
Thanks.
From:
Please see my blog post for an OpenSSL 3.0 and FIPS Update:
https://www.openssl.org/blog/blog/2019/02/13/FIPS-update/
Matt
--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
Hi Experts,
Looking for some assistance. I’ve compiled one of the App in FIPs mode and
while running the App. I’m getting fingerprint mismatch error. I’ve followed
the standard procedure to build a FIPS module using OpenSSL UserGuide 2.0. But
not sure what part is missing.
:~$ openssl
On 12/02/2019 22:29, Hal Murray wrote:
> Is there a better place for things like this?
>
> Please add X509_verify_cert_error_string to the SEE ALSO section of the man
> page for SSL_get_verify_result
Please raise an issue on github for this sort of thing. Even better create a
pull request.