Re: BC-FIPS does not reject JKS keystores

Daniel JeliƄski <[email protected]> Tue, 19 Nov 2019 08:30:38 +0100
Newsgroups gmane.comp.encryption.bouncy-castle.devel
Message-ID <CAMrH03Jrzj0xJTPD1k_qih4nN19opd15pLMS2O-r+3DG76TY-Q@mail.gmail.com>
--00000000000017e32d0597ae0b76
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Thanks David for your input. Yes I noticed that. The FIPS-related code was
actually removed from JDK some time ago, see
http://hg.openjdk.java.net/jdk/jdk/diff/cb1642ccc732/src/java.base/share/cl=
asses/sun/security/ssl/SunJSSE.java

Do you plan to replicate that functionality in BCTLS?
Thanks,
Daniel

wt., 19 lis 2019 o 07:50 David Hook <dgh-rTAZ0PM/[email protected]> napisa=C5=82(a=
):

>
> One other thing, FIPS mode in the regular JSSE provider started turning
> into a no-op with the arrival of Java 9. There's no assertion that the
> JSSE provider is compliant past Java 8.
>
> Regards,
>
> David
>
> On 19/11/19 1:25 pm, Peter Dettman wrote:
> > Hi Daniel,
> > If I'm understanding your question correctly, the answer is neither; th=
e
> > JSSE provider is not involved in certification for the FIPS jar itself.
> >
> > Regards,
> > Pete Dettman
> >
> > On 15/11/19 3:06 pm, Daniel Jeli=C5=84ski wrote:
> >> So, all is good. I'd just like to know which JSSE provider was
> >> BouncyCastle approved with, Sun's or BouncyCastleJsseProvider?
> >> Thanks,
> >> Daniel
> >
>
>
>

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

<div dir=3D"ltr">Thanks David for your input. Yes I noticed that. The FIPS-=
related code was actually removed from JDK some time ago, see=C2=A0

<a href=3D"http://hg.openjdk.java.net/jdk/jdk/diff/cb1642ccc732/src/java.ba=
se/share/classes/sun/security/ssl/SunJSSE.java">http://hg.openjdk.java.net/=
jdk/jdk/diff/cb1642ccc732/src/java.base/share/classes/sun/security/ssl/SunJ=
SSE.java</a><div><br></div><div>Do you plan to replicate that functionality=
 in BCTLS?</div><div>Thanks,</div><div>Daniel</div></div><br><div class=3D"=
gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">wt., 19 lis 2019 o 07:50=
=C2=A0David Hook &lt;<a href=3D"mailto:dgh-rTAZ0PM/[email protected]">dgh@cryptowo=
rkshop.com</a>&gt; napisa=C5=82(a):<br></div><blockquote class=3D"gmail_quo=
te" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204=
);padding-left:1ex"><br>
One other thing, FIPS mode in the regular JSSE provider started turning<br>
into a no-op with the arrival of Java 9. There&#39;s no assertion that the<=
br>
JSSE provider is compliant past Java 8.<br>
<br>
Regards,<br>
<br>
David<br>
<br>
On 19/11/19 1:25 pm, Peter Dettman wrote:<br>
&gt; Hi Daniel,<br>
&gt; If I&#39;m understanding your question correctly, the answer is neithe=
r; the<br>
&gt; JSSE provider is not involved in certification for the FIPS jar itself=
.<br>
&gt;<br>
&gt; Regards,<br>
&gt; Pete Dettman<br>
&gt;<br>
&gt; On 15/11/19 3:06 pm, Daniel Jeli=C5=84ski wrote:<br>
&gt;&gt; So, all is good. I&#39;d just like to know which JSSE provider was=
<br>
&gt;&gt; BouncyCastle approved with, Sun&#39;s or BouncyCastleJsseProvider?=
<br>
&gt;&gt; Thanks,<br>
&gt;&gt; Daniel<br>
&gt;<br>
<br>
<br>
</blockquote></div>

--00000000000017e32d0597ae0b76--