Several comments about David's proposal:
1. Only the initial ClientHellos are parsable.
===
The biggest problem I have with an Explorer-based design is that only
the initial ClientHello on a connection is passed in the clear.
Subsequent negotiations
On 9/29/2015 3:27 AM, Sean Mullan wrote:
Looks good, just a couple of comments:
AlgorithmId: can you use braces around the conditional statements on
lines 1008-1017?
OK.
Function: are you missing an @modules tag for the jarsigner module?
Which one? I thought @modules is only used if you
Looks good, just a couple of comments:
AlgorithmId: can you use braces around the conditional statements on
lines 1008-1017?
Function: are you missing an @modules tag for the jarsigner module?
Options.java: why not use the JarSigner API here instead of the
jarsigner tool?
--Sean
On 09/21/
> On Sep 25, 2015, at 3:22 PM, David M. Lloyd wrote:
>
> On 09/25/2015 02:11 PM, Simone Bordet wrote:
>> Hi,
>>
>> On Fri, Sep 25, 2015 at 7:23 PM, David M. Lloyd
>> wrote:
>>> The application protocol implementation chooses only valid cipher suites for
>>> the protocol. Why would it choose
Hello Usha,
I'm glad to hear that you're interested in this feature. As it turns
out, this feature is already part of OpenJDK 9. If you were to build
the JDK from source you should be able to take advantage of this
feature. If you do start using it I would love to hear feedback about
how t
Hi,
I am looking forward to the availability of OCSP stapling in OpenJDK 9. It
appears OpenJDK 9 will not become available till September/2016. How will this
functionality (OCSP stapling) be made available to the public after the JEP 249
project is resolved (current due date 11/06/15), and be
Hi,
I am looking forward to the availability of OCSP stapling in OpenJDK 9. It
appears OpenJDK 9 will not become available till September/2016. How will this
functionality (OCSP stapling) be made available to the public after the JEP 249
project is resolved (current due date 11/06/15)? Would i
