[jboss-remoting-commits] JBoss Remoting SVN: r3903 - remoting2/branches/2.x/src/etc.

jboss-remoting-commits at lists.jboss.org jboss-remoting-commits at lists.jboss.org
Sat Apr 5 01:24:32 EDT 2008


Author: ron.sigal at jboss.com
Date: 2008-04-05 01:24:32 -0400 (Sat, 05 Apr 2008)
New Revision: 3903

Modified:
   remoting2/branches/2.x/src/etc/remoting.security.policy.core
Log:
JBREM-920, JBREM-934: (1) Added java.io.FilePermission "*", "read, write"; for Identity;(2) replaced '/' with ${/} in file paths.

Modified: remoting2/branches/2.x/src/etc/remoting.security.policy.core
===================================================================
--- remoting2/branches/2.x/src/etc/remoting.security.policy.core	2008-04-04 22:58:55 UTC (rev 3902)
+++ remoting2/branches/2.x/src/etc/remoting.security.policy.core	2008-04-05 05:24:32 UTC (rev 3903)
@@ -40,7 +40,7 @@
     // This permission might need to be changed, depending on where the CallbackStore
     // is configured to exist, according to system property "jboss.server.data.dir".
     // The default location is <current directory>/data.
-    permission java.io.FilePermission "./data", "read, write, delete";
+    permission java.io.FilePermission ".${/}data", "read, write, delete";
     
     // Permission for org.jboss.remoting.ident.Identity to create and read "jboss.identity" file.
     // This permission might need to be changed, depending on the directory in which the
@@ -50,7 +50,7 @@
     // 2. the "jboss.identity.dir" system property, if that property exists, or
     // 3. the current directory.
     permission java.io.FilePermission ".", "read, write";
-//    permission java.io.FilePermission "-", "read, write";
+    permission java.io.FilePermission "*", "read, write";
     
     
 /////////////////////////////////////////////////////////////////////////////////////////////
@@ -198,10 +198,10 @@
 /////////////////////////////////////////////////////////////////////////////////////////////
 // TODO - We should use a version of JBoss logging + log4j that does this stuff in privileged blocks
 
-      permission java.io.FilePermission "${build.home}/src/etc/log4j.properties", "read";
-      permission java.io.FilePermission "${build.home}/src/etc/log4j.xml", "read";
-      permission java.io.FilePermission "${build.home}/lib/apache-log4j/lib/log4j.jar", "read";
-      permission java.io.FilePermission "${build.home}/output/classes/-", "read";
+      permission java.io.FilePermission "${build.home}${/}src${/}etc${/}log4j.properties", "read";
+      permission java.io.FilePermission "${build.home}${/}src${/}etc${/}log4j.xml", "read";
+      permission java.io.FilePermission "${build.home}${/}lib${/}apache-log4j${/}lib${/}log4j.jar", "read";
+      permission java.io.FilePermission "${build.home}${/}output${/}classes${/}-", "read";
       permission java.lang.RuntimePermission "accessClassInPackage.*";
       permission java.util.PropertyPermission "org.jboss.logging.Logger.pluginClass", "read";
       permission java.util.PropertyPermission "log4j.defaultInitOverride", "read";




More information about the jboss-remoting-commits mailing list