<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body><div>Hi Bernd,</div><div><br></div><div>For the status_request_v2 extension, both ocsp and ocsp_multi forms are supported, with preference on the latter type. The only feature we currently don't support right now is Responder ID selection, and that will hopefully come in a 9 update.</div><div><br></div><div id="composer_signature"><meta http-equiv="Content-Type" content="text/html; charset=UTF-8">--Jamil</div><div><br></div><div style="font-size:100%;color:#000000"><!-- originalMessage --><div>-------- Original message --------</div><div>From: Bernd Eckenfels <ecki@zusammenkunft.net> </div><div>Date: 8/11/16 3:00 PM (GMT-08:00) </div><div>To: security-dev@openjdk.java.net </div><div>Subject: Re: RFC7525 mapped to JSSE </div><div><br></div></div>Hello,<br><br>thank you Xuelei and Jamil. I updated the sheet and added an actual<br>column for Java 9. There are still some todos left (mostly for digging<br>up the detauls), but it starts to look complete now.<br><br>There are only two real non-compliances (for Java 9), that is the<br>support for HSTS in client code (not related to JSSE) and the fallback<br>signalling cipher (with limited usefullness).<br><br>For Java 8 the EC keySize < 224, can it be added?<br><br>For OCSP, the status_request(_v2), does it also support the multi<br>certificate variant?<br><br>https://docs.google.com/spreadsheets/d/135Eqf3RCpYLcmVHOIPb_Q7pzFde9yqJI_oD2jvpnKPE<br><br>Gruss<br>Bernd<br><br><br> Am Mon, 8 Aug 2016 08:57:29 +0800<br>schrieb Xuelei Fan <xuelei.fan@oracle.com>:<br><br>> Hi Bernd,<br>> <br>> Thanks for the summary of the compliance. The following comments are<br>> mainly about the items marked with "TODO" or "???".<br>> <br>> JDK 9 will support DTLS 1.0/1.2 and OCSP stapling (both RFC 6066 and<br>> RFC 6961).<br>> <br>> The server preference of cipher suites can be configurable.<br>> <br>> JDK uses uncompressed EC point format only.<br>> <br>> JDK does not use EC curves < 224 bits for EC key exchange, default<br>> 256+ bits.<br>> <br>> For TLS 1.2, SHA2 is requested in the signature algorithm extension.<br>> <br>> JDK does not implement the truncted HMAC extension.<br>> <br>> JDK supports hostname verification APIs for HTTPS, and support<br>> hostname verification during handshaking for HTTPS and LDAP.<br>> <br>> JDK tests the DH public keys.<br>> <br>> Thanks & Regards,<br>> Xuelei<br>> <br>> On 8/2/2016 6:13 AM, Bernd Eckenfels wrote:<br>> > Hello,<br>> > <br>> > because I was asked by a customer I started to map the RFC7525<br>> > <br>> > https://tools.ietf.org/html/rfc7525<br>> > <br>> > recommendations for TLS to JSSE implementation.<br>> > <br>> > <br>> > It is not complete yet but I think I at least have extraced all<br>> > "normative" requirements from the RFC into this table:<br>> > <br>> > https://docs.google.com/spreadsheets/d/135Eqf3RCpYLcmVHOIPb_Q7pzFde9yqJI_oD2jvpnKPE<br>> > <br>> > would like to get your feedback.<br>> > <br>> > Gruss<br>> > Bernd<br>> > <br>> <br><br></body></html>