Author: markt
Date: Tue Oct 4 13:33:02 2016
New Revision: 1763277
URL: http://svn.apache.org/viewvc?rev=1763277&view=rev
Log:
Remove additional references to the removed class JndiPermission
Modified:
tomcat/trunk/webapps/docs/security-manager-howto.xml
Modified: tomcat/trunk/webapps/docs/security-manager-howto.xml
URL:
http://svn.apache.org/viewvc/tomcat/trunk/webapps/docs/security-manager-howto.xml?rev=1763277&r1=1763276&r2=1763277&view=diff
==============================================================================
--- tomcat/trunk/webapps/docs/security-manager-howto.xml (original)
+++ tomcat/trunk/webapps/docs/security-manager-howto.xml Tue Oct 4 13:33:02
2016
@@ -105,40 +105,6 @@
</subsection>
-
- <subsection name="Tomcat Custom Permissions">
-
- <p>Tomcat utilizes a custom permission class called
- <strong>org.apache.naming.JndiPermission</strong>. This permission
- controls read access to JNDI named file based resources. The permission
- name is the JNDI name and there are no actions. A trailing "*" can be
- used to do wild card matching for a JNDI named file resource when
- granting permission. For example, you might include the following
- in your policy file:</p>
-<source>permission org.apache.naming.JndiPermission
"jndi://localhost/examples/*";</source>
-
- <p>A Permission entry like this is generated dynamically for each web
- application that is deployed, to allow it to read its own static resources
- but disallow it from using file access to read any other files (unless
- permissions for those files are explicitly granted).</p>
-
- <p>Also, Tomcat always dynamically creates the following file
permissions:</p>
-<source>
-permission java.io.FilePermission "** your application context**", "read";
-
-permission java.io.FilePermission
- "** application working directory**", "read,write";
-permission java.io.FilePermission
- "** application working directory**/-", "read,write,delete";
-</source>
- <p>Where **your application context** equals the folder (or WAR file)
under which
- your application has been deployed and **application working directory**
is the
- temporary directory provided to your application as required by the
- Servlet Specification.</p>
-
- </subsection>
-
-
</section>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
