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

[jboss-remoting-commits at lists.jboss.org]

Author: ron.sigal at jboss.com
Date: 2010-07-03 15:15:57 -0400 (Sat, 03 Jul 2010)
New Revision: 5899

Modified:
   remoting2/branches/2.x/src/etc/remoting.security.policy.core
Log:
JBREM-1231: Added RuntimePermission("invokerRegistryUpdate").

Modified: remoting2/branches/2.x/src/etc/remoting.security.policy.core
===================================================================
--- remoting2/branches/2.x/src/etc/remoting.security.policy.core	2010-07-03 19:03:02 UTC (rev 5898)
+++ remoting2/branches/2.x/src/etc/remoting.security.policy.core	2010-07-03 19:15:57 UTC (rev 5899)
@@ -27,8 +27,8 @@
 //****   with the permissions necessary to run the code in the org.jboss.remoting.*
 //****   packages.  All security sensitive calls in Remoting are wrapped in a
 //****   java.security.AccessController.doPrivileged() call, so that Remoting classes
-//****   can function in the context of a java.lang.SecurityManager, given the some
-//****   variation on the permissionslisted below, even if the calling code runs without
+//****   can function in the context of a java.lang.SecurityManager, given some
+//****   variation on the permissions listed below, even if the calling code runs without
 //****   these restrictions.
 //****
 //****   There are a few ways in which it may be necessary or desirable to modify the
@@ -176,7 +176,10 @@
     permission java.lang.RuntimePermission "loadLibrary.tcnative-1";
     permission java.lang.RuntimePermission "loadLibrary.libtcnative-1";
     
+    // Used to guard access to InvokerRegistry state
+    permission java.lang.RuntimePermission "invokerRegistryUpdate";
     
+    
 /////////////////////////////////////////////////////////////////////////////////////////////
 // Socket permissions.  Can't create sockets without it.