Hi Vladimir,
Indeed these are test issues that the tests will need to grant permissions
to jdk.internal.vm.compiler as the default policy grants.
Thanks for going extra miles to fix the tests.
My suggestion may be a bit general. What I intend to say the custom
security policy should extend the
On 6/19/2019 8:17 PM, Anthony Scarpino wrote:
On 6/19/19 5:02 PM, Xuelei Fan wrote:
Hi,
Could I get the following update reviewed?
http://cr.openjdk.java.net/~xuelei/8225766/webrev.01/
For TLS 1.2 and prior versions, the public key of a EC cert MUST use a
curve and point format suppor
On 6/19/19 5:02 PM, Xuelei Fan wrote:
Hi,
Could I get the following update reviewed?
http://cr.openjdk.java.net/~xuelei/8225766/webrev.01/
For TLS 1.2 and prior versions, the public key of a EC cert MUST use a
curve and point format supported by the client. But in TLS 1.3,
signature algo
http://cr.openjdk.java.net/~kvn/8185139/webrev.00/
https://bugs.openjdk.java.net/browse/JDK-8185139
For Graal to work we have to give Graal module all permissions which is
specified in default policy [1].
Unfortunately this cause problem for Graal running tests which overwrite
default policy.
Hi,
Could I get the following update reviewed?
http://cr.openjdk.java.net/~xuelei/8225766/webrev.01/
For TLS 1.2 and prior versions, the public key of a EC cert MUST use a
curve and point format supported by the client. But in TLS 1.3,
signature algorithms are negotiated independently via
