glenn 01/06/29 11:01:41
Modified: catalina/docs tomcat-security.html
Log:
Update policy for WebappClassLoader changes
Revision Changes Path
1.3 +9 -21 jakarta-tomcat-4.0/catalina/docs/tomcat-security.html
Index: tomcat-security.html
===================================================================
RCS file: /home/cvs/jakarta-tomcat-4.0/catalina/docs/tomcat-security.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- tomcat-security.html 2001/06/26 21:00:30 1.2
+++ tomcat-security.html 2001/06/29 18:01:37 1.3
@@ -156,7 +156,7 @@
//
// * Read access to the document root directory
//
-// $Id: tomcat-security.html,v 1.2 2001/06/26 21:00:30 glenn Exp $
+// $Id: tomcat-security.html,v 1.3 2001/06/29 18:01:37 glenn Exp $
// ============================================================================
@@ -279,37 +279,25 @@
// For instance, assume that the standard "examples" application
// included a JDBC driver that needed to establish a network connection to the
// corresponding database and used the scrape taglib to get the weather from
-// the NOAA web server. You might create a "grant" entries like this:
+// the NOAA web server. You might create a "grant" entries like this:
//
// The permissions granted to the context root directory apply to JSP pages.
// grant codeBase "file:${catalina.home}/webapps/examples/-" {
-// permission java.net.SocketPermission
"dbhost.mycompany.com:5432", "connect";
-// permission java.net.SocketPermission
"*.noaa.gov:80", "connect";
-//
+// permission java.net.SocketPermission "dbhost.mycompany.com:5432", "connect";
+// permission java.net.SocketPermission "*.noaa.gov:80", "connect";
// };
//
// The permissions granted to the context WEB-INF/classes directory
-//
-// Permissions granted to a web applications /WEB-INF/classes
-// need to use the JNDI naming convention Tomcat 4 uses to identify
-// these resources. The naming convention is
-// "jndi:/<virtual host name>/<web application directory>/WEB-INF/classes/
-//
-// grant codeBase "jndi:/localhost/examples/WEB-INF/classes/-" {
+// grant codeBase "file:${catalina.home}/webapps/examples/WEB-INF/classes/-" {
// };
//
-// Permissions granted to a web applications /WEB-INF/lib
-// need to use the JNDI naming convention Tomcat 4 uses to identify
-// these resources. The naming convention is
-// "jar:jndi:/<virtual host name>/<web application directory>/WEB-INF/lib/
-//
// The permission granted to your JDBC driver
-// grant codeBase "jar:jndi:/localhost/examples/WEB-INF/lib/driver.jar" {
-// permission java.net.SocketPermission
"dbhost.mycompany.com:5432", "connect";
+// grant codeBase
"file:${catalina.home}/webapps/examples/WEB-INF/lib/driver.jar!/-" {
+// permission java.net.SocketPermission "dbhost.mycompany.com:5432", "connect";
// };
// The permission granted to the scrape taglib
-// grant codeBase "jar:jndi:localhost/webapps/examples/WEB-INF/lib/scrape.jar" {
-// permission java.net.SocketPermission
"*.noaa.gov:80", "connect";
+// grant codeBase
"file:${catalina.home}/webapps/examples/WEB-INF/lib/scrape.jar!/-" {
+// permission java.net.SocketPermission "*.noaa.gov:80", "connect";
// };</pre>
</td>
</tr>
