OK thanks. I had been looking for your name in that list.
In addition, changesets require a testcase to verify the fix so I've modified
an existing keychain testcase.
I’ve updated the previous webrev, in place:
http://cr.openjdk.java.net/~vinnie/8062264/webrev.00/
On 28 Oct 2014, at 11:12,
Looks fine to me.
--Sean
On 10/28/2014 02:42 PM, Vincent Ryan wrote:
OK thanks. I had been looking for your name in that list.
In addition, changesets require a testcase to verify the fix so I've
modified an existing keychain testcase.
I’ve updated the previous webrev, in place:
http://cr.ope
Hello All,
I've spent the last 6 months working with some colleagues on a project
that aimed to stop an exploitation avenue that has been popular with
recent Java exploits: disabling the security manager. We think that what
ended up with may be worthy of a JEP and/or a prototype implementation
On 10/29/2014 08:35 AM, Michael Maass wrote:
Hello All,
I've spent the last 6 months working with some colleagues on a project
that aimed to stop an exploitation avenue that has been popular with
recent Java exploits: disabling the security manager. We think that what
ended up with may be worthy
Hi,
Another update on the subject.
It seems that the HTTP 2.0 working group has relaxed, after a
excruciating battle, requirements on ciphers and their entanglement
with the ALPN protocols advertised.
This results in many less requirements to have ALPN and HTTP 2.0 work together.
I am reviewing
Please review this fix contributed by David Kocher.
It corrects an issue in the Keychain keystore implementation for Mac OS where
private keys
configured with a key usage other than ‘any’ are not retrieved.
Bug: https://bugs.openjdk.java.net/browse/JDK-8046777
Webrev: http://cr.openjdk.java.net/
