jdk-24/jdk/test/java/rmi/activation/CommandEnvironment/security.policy
Valerie Peng efa54ce543 8043406: Change default policy for JCE providers to run with as few privileges as possible
Provide default permissions for crypto providers

Reviewed-by: mullan, vinnie
2014-07-10 22:44:58 +00:00

33 lines
1.3 KiB
Plaintext

/*
* security policy used by the test process
*/
grant {
// standard test activation permissions
permission java.io.FilePermission "..${/}..${/}test.props", "read";
// test needs to cleanup rmid's log.
permission java.io.FilePermission ".${/}log", "read,write,delete";
permission java.io.FilePermission ".${/}log${/}-", "read,write,delete";
// test needs to use java to exec an rmid
permission java.io.FilePermission "${java.home}${/}bin${/}java", "execute";
// test uses these permissions to propagate security values to rmid
permission java.util.PropertyPermission "java.security.policy", "read";
permission java.util.PropertyPermission "java.security.manager", "read";
permission java.util.PropertyPermission "java.compiler", "read";
// used by TestLibrary to determine test environment
permission java.util.PropertyPermission "test.*", "read";
permission java.util.PropertyPermission "user.dir", "read";
permission java.util.PropertyPermission "java.home", "read";
permission java.util.PropertyPermission "java.rmi.activation.port", "write";
// required for test to create an ActivationGroup
permission java.lang.RuntimePermission "setFactory";
// test needs to export rmid and communicate with objects on arbitrary ports
permission java.net.SocketPermission "*:1024-", "connect,accept,listen";
};