<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);" class="">Hello,</span><br class="" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);"><br class="" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);"><span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);" class="">I have been working on this issue for some time already.</span><br class="" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);"><span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);" class="">The patch below adds java.net.SocketTimeoutException handling during TLS handshake negotiation. This functionality seems to have been missed during the TLSv1.3 implementation ( JDK-8196584 )</span><br class="" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);"><span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);" class="">Tested with JDK11 and higher. </span><br class="" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);"><br class="" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);"><span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);" class="">JDK11 webrev: </span><a href="http://cr.openjdk.java.net/~yan/8239788/webrev.0/" class="">http://cr.openjdk.java.net/~yan/8239788/webrev.0/</a><div class="" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);"><span class="" style="font-family: HelveticaNeue;"><br class=""></span></div><div class="" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);"><span class="" style="font-family: HelveticaNeue;">jbs: </span><font face="HelveticaNeue" class=""><a href="https://bugs.openjdk.java.net/browse/JDK-8239798" class="">https://bugs.openjdk.java.net/browse/JDK-8239798</a> and </font><span class="" style="font-family: HelveticaNeue;"><a href="https://bugs.openjdk.java.net/browse/JDK-8239788" class="">https://bugs.openjdk.java.net/browse/JDK-8239788</a></span><div class=""><font face="HelveticaNeue" class=""><br class=""></font><div class=""><span class="">Thank you,</span><div class=""><span class="">Alexey</span></div></div></div></div><div><br class=""><blockquote type="cite" class=""><div class="">On 22 Feb 2020, at 15:00, <a href="mailto:security-dev-request@openjdk.java.net" class="">security-dev-request@openjdk.java.net</a> wrote:</div><div class=""><div class=""><br class="">I will look into the issue.<br class=""><br class="">BTW, I closed JDK-8239788 as duplicate of JDK-8239798.<br class=""><br class="">Thanks,<br class="">Xuelei<br class=""><br class="">On 2/21/2020 9:24 AM, Kumar Srinivasan wrote:<br class=""><blockquote type="cite" class="">Hi security-folk,<br class=""><br class="">At VMware while upgrading our application to OpenJDK11u, we have <br class="">encountered what seems to be a serious behavior issue.<br class="">The issue AFAICT seems to have stemmed from the work for TLS1.3 and <br class="">JDK-8196584 <<a href="https://bugs.openjdk.java.net/browse/JDK-8196584" class="">https://bugs.openjdk.java.net/browse/JDK-8196584</a>>.<br class=""><br class="">Overview:<br class="">With OpenJDK11 the end-points are closed immediately with TLS alerts <br class="">raised when an exception is received.<br class="">This is not the case with JDK8 the socket is not closed allowing retries.<br class=""><br class="">I have filed: JDK-8239798 (with a reproducer), this issue was also <br class="">reported ?to Azul and they have filed: JDK-8239788.<br class=""><br class="">Can you please evaluate this at the earliest, this is a serious show <br class="">stopper for VMware.<br class=""><br class="">Thank<br class="">Kumar Srinivasan<br class="">VMware<br class=""></blockquote><br class=""></div></div></blockquote></div><br class=""></body></html>