Please review this fix to only grant the necessary PropertyPermissions
to the jdk.crypto.ucrypto module.
In UcryptoProvider I also moved the System.getProperty("os.name") inside
doPrivileged (just in case permission to read this property has not been
granted to the caller) and did some minor r
On 10/13/2016 01:29 AM, Anthony Scarpino wrote:
On 10/12/2016 01:41 PM, Sean Mullan wrote:
On 10/12/2016 04:06 PM, Anthony Scarpino wrote:
Later in the verify(), AlgorithmChecker needs a TrustAnchor object. In
this case, because it's the old method that deploy is using, I have to
manufacture a
Hi,
Please review the fix for JDK-8167680:
http://cr.openjdk.java.net/~xuelei/8167680/webrev.00/
There are a few implementation bugs in JDK.
1. The sequence number is increased by 2 for GCM cipher suites.
Both GCM crypto operation and DTLS record use the sequence number. The
current implem
Nice catch! Looks fine to me.
Xuelei
On 10/13/2016 6:33 PM, Vincent Ryan wrote:
Please review this fix to add a check to the default implementation of KeyStore
setEntry and getEntry (in KeyStoreSpi).
An exception is thrown if a password protection algorithm is specified. An
existing test has
Please review this fix to add a check to the default implementation of KeyStore
setEntry and getEntry (in KeyStoreSpi).
An exception is thrown if a password protection algorithm is specified. An
existing test has been updated to validate the fix.
Keystore implementations that support a user-supp
