This is great. Change looks fine to me.
Thanks
Max
On 8/18/2016 23:28, Seán Coffey wrote:
Thanks for the tip Artem, Max. No need to modify the policy file then.
Below is the new suggested patch for jdk8u-dev. JPRT results are good.
diff --git a/test/sun/security/krb5/auto/UnboundSSL.java
b/tes
Hi Sean,
The patch below looks fine to me, but I am not an official reviewer.
Artem
On 08/18/2016 08:28 AM, Seán Coffey wrote:
Thanks for the tip Artem, Max. No need to modify the policy file then.
Below is the new suggested patch for jdk8u-dev. JPRT results are good.
diff --git a/test/sun/
Thanks for the tip Artem, Max. No need to modify the policy file then.
Below is the new suggested patch for jdk8u-dev. JPRT results are good.
diff --git a/test/sun/security/krb5/auto/UnboundSSL.java
b/test/sun/security/krb5/auto/UnboundSSL.java
--- a/test/sun/security/krb5/auto/UnboundSSL.java
If I recall correctly, there should be a way to specify a policy file
in @run without overriding the default one. May be it is "@run
main/othervm/java.security.policy=unbound.ssl.policy_new"
Yes, I think this should work. I've also just learned about it and don't
know from which jtreg it is sup
Sorry, my bad, I didn't notice '9-na' label.
I suppose that code from ext directory should have all permissions:
artem@artem-laptop:$ cat ~/jdk/jdk1.8.0_92b14/jre/lib/security/java.policy
// Standard extensions get all permissions by default
grant codeBase "file:${{java.ext.dirs}}/*" {
Hi Artem,
Sorry - should have said that this is for jdk8u-dev. The bug is marked
9-na. The provider loading changes made in this area for 9 mean that
it's not affected.
Regards,
Sean.
On 17/08/16 18:10, Artem Smotrakov wrote:
Hi Sean,
If I remember correctly, there is no ext directory in J
Hi Sean,
If I remember correctly, there is no ext directory in JDK 9 any more.
I don't see in jtr file that "java.ext.dirs" system property is passed
to the test. If I understand correctly, "file:${{java.ext.dirs}}/*"
becomes "file:/*" which seems to grand all permissions to all the code.
It
A recently added test case lacks sufficient permissions to read a conf
file when running with security manager.
bug report : https://bugs.openjdk.java.net/browse/JDK-8162916
proposed patch :
diff --git a/test/sun/security/krb5/auto/unbound.ssl.policy
b/test/sun/security/krb5/auto/unbound.ssl.
