Re: OpenSSL and PQC/FIPS support

--00000000000036dbdb064f800a82
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Raghu-
     PQC algorithms approved by FIPS include FIPS 203 (ML-KEM), FIPS 204
(ML-DSA) and FIPS 205 (SLH-DSA).  These are supported currently only by the
3.5.4 FIPS provider and later versions.  Currently 3.5.4 is undergoing
review with our lab and NIST:
https://csrc.nist.gov/projects/cryptographic-module-validation-program/modu=
les-in-process/modules-in-process-list


FIPS and PQC are definitely _not_ mutually exclusive, you can
definitely use both PQC algorithms and be FIPS-140-3 compliant.  The only
current barrier is that our provider has not yet been certified by NIST.
That need not be a barrier for you however, if you are planning on doing a
full submission of openssl through your own lab (though the time effort on
that is constrained by your lab and NIST).

Neil


On Wed, Apr 15, 2026 at 9:43=E2=80=AFAM Raghu Chidambaram <pcraghu.prasad@g=
mail.com>
wrote:

> Hi Team,
>
> Our organization is planning to go for PQC support so that application is
> quantum safe.
> we are already FIPS 140-2 compliant and we are also in the process of
> making it FIPS 140-3 compliant as 140-2 will be sunset by Sep 2026.
>
> FIPS
> - Our application is FIPS 140-2 and with FIPS provider 3.0.9. We made thi=
s
> possible with the help of lot of to and fro discussions over the OpenSSL
> Forum for good amount of time :) :) .
>
> For 140-3 we did analysis and understood that with OpenSSL version say
> 3.5.x we need to bundle the FIPS provider version 3.1.2 ( 140-3 compliant=
 )
> instead of 3.0.9( 140-2) compliant. Hope this is correct.
>
> PQC
> - For PQC we just started analysis and checking which all algorithms we
> need to use in order to make it PQC compliant. As part of this we want to
> understand which of OpenSSL supports PQC and is there any doc / list whic=
h
> conveys like from algorithm A we need to move to algorithm, means how to
> migrate from current set to PQC safe set is what we are checking mainly.
>
> - one more point what we understood from the discussions internally and
> with the teams who are handling inside our organization that FIPS and PQC
> cant go hand in hand, like if we are in FIPS 140-3 version we cant claim
> for PQC as algo's are different and if we are going to be PQC safe then w=
e
> can't claim FIPS 140-3 support, is this correct statement? or our
> assumption is wrong?
>
> Need your help and inputs to proceed on these aspects
>
> Thank you,
> Raghu
>
> --
> You received this message because you are subscribed to the Google Groups
> "openssl-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to openssl-users+unsubscribe-MCmKBN63+Bmbup2nOX2J7Q@public.gmane.org
> To view this discussion visit
> https://groups.google.com/a/openssl.org/d/msgid/openssl-users/9d605db8-92=
20-491c-9424-12b42ed92948n%40openssl.org
> <https://groups.google.com/a/openssl.org/d/msgid/openssl-users/9d605db8-9=
220-491c-9424-12b42ed92948n%40openssl.org?utm_medium=3Demail&utm_source=3Df=
ooter>
> .
>

--=20
You received this message because you are subscribed to the Google Groups "=
openssl-users" group.
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to openssl-users+unsubscribe-MCmKBN63+Bmbup2nOX2J7Q@public.gmane.org
To view this discussion visit https://groups.google.com/a/openssl.org/d/msg=
id/openssl-users/CAJbOq16tR2n_U1tWtzbCUzt57PjEZQbiJRjvM-3vPQ3gkrGyXA%40mail=
.gmail.com.

--00000000000036dbdb064f800a82
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Raghu-<div>=C2=A0 =C2=A0 =C2=A0PQC algorithms approved by =
FIPS include FIPS 203 (ML-KEM), FIPS 204 (ML-DSA) and FIPS 205 (SLH-DSA).=
=C2=A0 These are supported currently only by the 3.5.4 FIPS provider and la=
ter versions.=C2=A0 Currently 3.5.4 is undergoing review with our lab and N=
IST:</div><div><a href=3D"https://csrc.nist.gov/projects/cryptographic-modu=
le-validation-program/modules-in-process/modules-in-process-list">https://c=
src.nist.gov/projects/cryptographic-module-validation-program/modules-in-pr=
ocess/modules-in-process-list</a></div><div><br></div><div><br></div><div>F=
IPS and PQC are definitely=C2=A0_not_ mutually exclusive, you can definitel=
y=C2=A0use both PQC algorithms and be FIPS-140-3 compliant.=C2=A0 The only =
current barrier is that our provider has not yet been certified by NIST.=C2=
=A0 That need not be a barrier for you however, if you are planning on doin=
g a full submission of openssl through your own lab (though the time effort=
 on that is constrained by your lab and NIST).</div><div><br></div><div>Nei=
l</div><div><br></div></div><br><div class=3D"gmail_quote gmail_quote_conta=
iner"><div dir=3D"ltr" class=3D"gmail_attr">On Wed, Apr 15, 2026 at 9:43=E2=
=80=AFAM Raghu Chidambaram &lt;<a href=3D"mailto:[email protected]">=
[email protected]</a>&gt; wrote:<br></div><blockquote class=3D"gmail=
_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204=
,204);padding-left:1ex">Hi Team,<div><br></div><div>Our organization is pla=
nning to go for PQC support so that application is quantum safe.</div><div>=
we are already FIPS 140-2 compliant and we are also in the process of makin=
g it FIPS 140-3 compliant as 140-2 will be sunset by Sep 2026.</div><div><b=
r></div><div>FIPS</div><div>- Our application is FIPS 140-2 and with FIPS p=
rovider 3.0.9. We made this possible with the help of lot of to and fro dis=
cussions over the OpenSSL Forum for good amount of time :) :) .</div><div><=
br></div><div>For 140-3 we did analysis and understood that with OpenSSL ve=
rsion say 3.5.x we need to bundle the FIPS provider version 3.1.2 ( 140-3 c=
ompliant ) instead of 3.0.9( 140-2) compliant. Hope this is correct.<br><br=
>PQC</div><div>- For PQC we just started analysis and checking which all al=
gorithms we need to use in order to make it PQC compliant. As part of this =
we want to understand which of OpenSSL supports PQC and is there any doc / =
list which conveys like from algorithm A we need to move to algorithm, mean=
s how to migrate from current set to PQC safe set is what we are checking m=
ainly.=C2=A0<br><br>- one more point what we understood from the discussion=
s internally and with the teams who are handling inside our organization th=
at FIPS and PQC cant go hand in hand, like if we are in FIPS 140-3 version =
we cant claim for PQC as algo&#39;s are different and if we are going to be=
 PQC safe then we can&#39;t claim FIPS 140-3 support, is this correct state=
ment? or our assumption is wrong?</div><div><br></div><div>Need your help a=
nd inputs to proceed on these aspects=C2=A0</div><div><br></div><div>Thank =
you,</div><div>Raghu</div>

<p></p>

-- <br>
You received this message because you are subscribed to the Google Groups &=
quot;openssl-users&quot; group.<br>
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:openssl-users+unsubscribe-MCmKBN63+BlAfugRpC6u6w@public.gmane.org" target=3D"=
_blank">openssl-users+unsubscribe-MCmKBN63+BlAfugRpC6u6w@public.gmane.org</a>.<br>
To view this discussion visit <a href=3D"https://groups.google.com/a/openss=
l.org/d/msgid/openssl-users/9d605db8-9220-491c-9424-12b42ed92948n%40openssl=
.org?utm_medium=3Demail&amp;utm_source=3Dfooter" target=3D"_blank">https://=
groups.google.com/a/openssl.org/d/msgid/openssl-users/9d605db8-9220-491c-94=
24-12b42ed92948n%40openssl.org</a>.<br>
</blockquote></div>

<p></p>

-- <br />
You received this message because you are subscribed to the Google Groups &=
quot;openssl-users&quot; group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:openssl-users+unsubscribe-MCmKBN63+BlAfugRpC6u6w@public.gmane.org">openssl-us=
[email protected]</a>.<br />
To view this discussion visit <a href=3D"https://groups.google.com/a/openss=
l.org/d/msgid/openssl-users/CAJbOq16tR2n_U1tWtzbCUzt57PjEZQbiJRjvM-3vPQ3gkr=
GyXA%40mail.gmail.com?utm_medium=3Demail&utm_source=3Dfooter">https://group=
s.google.com/a/openssl.org/d/msgid/openssl-users/CAJbOq16tR2n_U1tWtzbCUzt57=
PjEZQbiJRjvM-3vPQ3gkrGyXA%40mail.gmail.com</a>.<br />

--00000000000036dbdb064f800a82--