Re: An update on ecosystem concerns removing javax.security.cert

2023-04-15 Thread Eirik Bjørsnøs
> > The changes in JDK-8241047 were intended to allow SSLSession > implementations drop their dependence on > javax.security.cert.X509Certificate but it may take time if implementations > are still expecting to be able to compile to a wide range of releases that > include JDK 14 or older. JDK-824

Re: An update on ecosystem concerns removing javax.security.cert

2023-04-15 Thread Alan Bateman
On 15/04/2023 10:15, Eirik Bjørsnøs wrote: Hi, JDK-8227024 [1] and the associated CSR JDK-8227395 [2] suggests removing the deprecated classes in javax.security.cert. The CSR was withdrawn last year following ecosystem compatibility concerns: Given the compatibility risks/impacts with

Re: An update on ecosystem concerns removing javax.security.cert

2023-04-15 Thread Eirik Bjørsnøs
On Sat, Apr 15, 2023 at 11:15 AM Eirik Bjørsnøs wrote: > Based on my recent interaction with these projects I'm hopeful that the > ecosystem impact is lower than what has been assessed previously. > Neither Jetty nor Grizzly have dependencies on javax.servlet.cert in their mainline code bases.

An update on ecosystem concerns removing javax.security.cert

2023-04-15 Thread Eirik Bjørsnøs
Hi, JDK-8227024 [1] and the associated CSR JDK-8227395 [2] suggests removing the deprecated classes in javax.security.cert. The CSR was withdrawn last year following ecosystem compatibility concerns: Given the compatibility risks/impacts with existing providers and JSSE > implementations, we've

Re: Could we backport the default SSLSession.getPeerCertificateChain method to 11?

2023-04-15 Thread Eirik Bjørsnøs
Sean, On Fri, Apr 14, 2023 at 9:18 PM Sean Mullan wrote: > Not possible right now AFAICT, but I will keep it in mind as a candidate > API change for the next MR, if and when that may occur. Thanks for your analysis, this was enlightening. Too bad our timing is off, but such is life :-) I foun