>We won't be offering the service to add new platforms onto our own
> certificate,
but you should be able perform your own validation for your own platforms
based
on ours (I forget the correct FIPS term for this...perhaps someone more
FIPSy
than I am can chip in).
Vendor-affir
org; openssl-us...@openssl.org;
> openssl-project@openssl.org
> *Subject:* [openssl-project] OpenSSL 3.0 and FIPS Update
>
> 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-project@openssl.org
Subject: [openssl-project] OpenSSL 3.0 and FIPS Update
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-project mailing list
openssl-project
On Wed, Feb 13, 2019 at 03:28:30PM -0500, Michael Richardson wrote:
>
> 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.
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
repr
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-project mailing list
openssl-project@openssl.org
https://mta.openssl.org/mailman/listinfo/openssl-project
