RFR: 8259662: Don't wrap SocketExceptions into SSLExceptions in SSLSocketImpl [v6]

Clive Verghese cverghese at openjdk.java.net
Fri Jan 29 08:40:45 UTC 2021


On Thu, 28 Jan 2021 19:04:29 GMT, Xue-Lei Andrew Fan <xuelei at openjdk.org> wrote:

>> Clive Verghese has updated the pull request with a new target base due to a merge or a rebase.
>
> src/java.base/share/classes/sun/security/ssl/SSLSocketImpl.java line 1702:
> 
>> 1700:             if (!conContext.isInboundClosed()) {
>> 1701:                 try {
>> 1702:                     decode(null);
> 
> One decode may be not sufficient if there are multiple pending handshake messages record, or the connection has been established and application data transportation is in progress.  I'm not sure if an additional decode() here really solve the problem as described in JDK-8259516.
> 
> I did not follow the issue of JDK-8259516.  Why an SSLException is desired but not SocketException, as if the socket has been closed?

I have removed issues for JDK-8259516.

-------------

PR: https://git.openjdk.java.net/jdk/pull/2057


More information about the security-dev mailing list