Re: ECDSA cert and TLS_ECDHE_ECDSA_WITH_AES_128_CCM_8
Jiho Park(박지호) <[email protected]>
| Newsgroups | gmane.comp.encryption.bouncy-castle.devel |
|---|---|
| Message-ID | <CACE8fQQoCn1xEgkTuF-u0S8z5ym96gcNZ=QyRgXWhmYTvuWRZg@mail.gmail.com> |
Hi Pete,
I resolve the issue with your comment . (I prefer to set by java code)
Security.setProperty("ssl.KeyManagerFactory.algorithm", "PKIX");
Thank you!
2018-06-20 20:19 GMT+09:00 Peter Dettman <[email protected]>:
> Hi Jiho,
>
> The BCJSSE TLS server currently only works properly with its own
> KeyManagerFactory, though RSA credentials may work OK in some cases
> without it. The BCJSSE KMF is registered for the "PKIX" algorithm.
> Probably you just need to edit the entry in jre/lib/security/java.policy
> file:
>
> #ssl.KeyManagerFactory.algorithm=SunX509
> ssl.KeyManagerFactory.algorithm=PKIX
>
> Another option might be to use KeyManagerFactory.getInstance("PKIX") if
> you are calling it explicitly.
>
> Regards,
> Pete Dettman
>
>
> On 20/6/18 3:17 pm, Jiho Park(박지호) wrote:
> > Hello, everyone.
> > first of all, thank you for .
> >
> > I'm trying to test HTTPS communication with ECDSA certificate and
> > TLS_ECDHE_ECDSA_WITH_AES_128_CCM_8.
> > But it fails to handshake
> >
> >
> > Server-side)
> > - Java 8, Spring Boot(embedded tomcat)
> > - bcprov-jdk15on-159, bctls-jdk15on-159
> > - add BC Provider, BCJSSE Provider at the first of provider list
> > - Enabled Ciphers : TLS_ECDHE_ECDSA_WITH_AES_128_CCM_8,
> > TLS_RSA_WITH_AES_256_CBC_SHA256
> > - set TLS related properties in application.properties
>
>