Code Review Request, JDK-8208166, Still unable to use custom SSLEngine with default TrustManagerFactory after JDK-8207029

Xuelei Fan xuelei.fan at oracle.com
Mon Jul 30 17:57:10 UTC 2018


Hi Norman,

Would you mind look at the code I posted in the following thread:
http://mail.openjdk.java.net/pipermail/security-dev/2018-July/017708.html

I appreciate if you could have a test by the end of this week.

Note that with this update, a complete TLS connection should close both 
inbound and outbound explicitly.  However, existing applications may not 
did this way.  If the source code update is not available, please 
consider to use the "jdk.tls.acknowledgeCloseNotify" as a workaround.

Thanks,
Xuelei

On 7/25/2018 11:22 PM, Norman Maurer wrote:
> Just FYI… I tested this patch via the netty ssl tests and we no longer 
> see the class-cast-exception problems I reported before dso I think this 
> solves the issue.
> 
> 
> That said we still encounter a few test-failures for tests that test 
> behaviour of closing outbound of the SSLEngine but I think these are 
> more related to 
> http://mail.openjdk.java.net/pipermail/security-dev/2018-July/017633.html and 
> http://mail.openjdk.java.net/pipermail/security-dev/2018-July/017566.html .
> 
> Bye
> Norman
> 
> 
> 
>> On 25. Jul 2018, at 20:30, Xuelei Fan <xuelei.fan at oracle.com 
>> <mailto:xuelei.fan at oracle.com>> wrote:
>>
>> Hi,
>>
>> Please review the update for JDK-8208166:
>> http://cr.openjdk.java.net/~xuelei/8208166/webrev.00/ 
>> <http://cr.openjdk.java.net/%7Exuelei/8208166/webrev.00/>
>> https://bugs.openjdk.java.net/browse/JDK-8208166
>>
>> Thanks,
>> Xuelei
> 


More information about the security-dev mailing list