359 lines
30 KiB
HTML
359 lines
30 KiB
HTML
<html><head><META http-equiv="Content-Type" content="text/html; charset=iso-8859-1"><title>Apache Tomcat 6.0 - Security Manager HOW-TO</title><meta name="author" value="Glenn Nielsen"><meta name="email" value="glenn@voyager.apg.more.net"><meta name="author" value="Jean-Francois Arcand"><meta name="email" value="jeanfrancois.arcand@sun.com"></head><body bgcolor="#ffffff" text="#000000" link="#525D76" alink="#525D76" vlink="#525D76"><table border="0" width="100%" cellspacing="0"><!--PAGE HEADER--><tr><td><!--PROJECT LOGO--><a href="http://tomcat.apache.org/"><img src="./images/tomcat.gif" align="right" alt="
|
|
The Apache Tomcat Servlet/JSP Container
|
|
" border="0"></a></td><td><font face="arial,helvetica,sanserif"><h1>Apache Tomcat 6.0</h1></font></td><td><!--APACHE LOGO--><a href="http://www.apache.org/"><img src="./images/asf-logo.gif" align="right" alt="Apache Logo" border="0"></a></td></tr></table><table border="0" width="100%" cellspacing="4"><!--HEADER SEPARATOR--><tr><td colspan="2"><hr noshade="noshade" size="1"></td></tr><tr><!--LEFT SIDE NAVIGATION--><td width="20%" valign="top" nowrap="true"><p><strong>Links</strong></p><ul><li><a href="index.html">Docs Home</a></li><li><a href="http://tomcat.apache.org/faq">FAQ</a></li></ul><p><strong>User Guide</strong></p><ul><li><a href="introduction.html">1) Introduction</a></li><li><a href="setup.html">2) Setup</a></li><li><a href="appdev/index.html">3) First webapp</a></li><li><a href="deployer-howto.html">4) Deployer</a></li><li><a href="manager-howto.html">5) Manager</a></li><li><a href="realm-howto.html">6) Realms and AAA</a></li><li><a href="security-manager-howto.html">7) Security Manager</a></li><li><a href="jndi-resources-howto.html">8) JNDI Resources</a></li><li><a href="jndi-datasource-examples-howto.html">9) JDBC DataSources</a></li><li><a href="class-loader-howto.html">10) Classloading</a></li><li><a href="jasper-howto.html">11) JSPs</a></li><li><a href="ssl-howto.html">12) SSL</a></li><li><a href="ssi-howto.html">13) SSI</a></li><li><a href="cgi-howto.html">14) CGI</a></li><li><a href="proxy-howto.html">15) Proxy Support</a></li><li><a href="mbeans-descriptor-howto.html">16) MBean Descriptor</a></li><li><a href="default-servlet.html">17) Default Servlet</a></li><li><a href="cluster-howto.html">18) Clustering</a></li><li><a href="balancer-howto.html">19) Load Balancer</a></li><li><a href="connectors.html">20) Connectors</a></li><li><a href="monitoring.html">21) Monitoring and Management</a></li><li><a href="logging.html">22) Logging</a></li><li><a href="apr.html">23) APR</a></li><li><a href="virtual-hosting-howto.html">24) Virtual Hosting</a></li><li><a href="aio.html">25) Advanced IO</a></li><li><a href="extras.html">26) Additional Components</a></li><li><a href="maven-jars.html">27) Mavenized</a></li></ul><p><strong>Reference</strong></p><ul><li><a href="RELEASE-NOTES.txt">Release Notes</a></li><li><a href="config/index.html">Configuration</a></li><li><a href="api/index.html">Javadocs</a></li><li><a href="http://tomcat.apache.org/connectors-doc/">JK 1.2 Documentation</a></li></ul><p><strong>Apache Tomcat Development</strong></p><ul><li><a href="building.html">Building</a></li><li><a href="changelog.html">Changelog</a></li><li><a href="status.html">Status</a></li><li><a href="developers.html">Developers</a></li><li><a href="architecture/index.html">Architecture</a></li><li><a href="funcspecs/index.html">Functional Specs.</a></li></ul></td><!--RIGHT SIDE MAIN BODY--><td width="80%" valign="top" align="left"><table border="0" width="100%" cellspacing="4"><tr><td align="left" valign="top"><h1>Apache Tomcat 6.0</h1><h2>Security Manager HOW-TO</h2></td><td align="right" valign="top" nowrap="true"><small><a href="printer/security-manager-howto.html"><img src="./images/printer.gif" border="0" alt="Printer Friendly Version"><br>print-friendly<br>version
|
|
</a></small></td></tr></table><table border="0" cellspacing="0" cellpadding="2"><tr><td bgcolor="#525D76"><font color="#ffffff" face="arial,helvetica.sanserif"><a name="Background"><strong>Background</strong></a></font></td></tr><tr><td><blockquote>
|
|
|
|
<p>The Java <strong>SecurityManager</strong> is what allows a web browser
|
|
to run an applet in its own sandbox to prevent untrusted code from
|
|
accessing files on the local file system, connecting to a host other
|
|
than the one the applet was loaded from, and so on. In the same way
|
|
the SecurityManager protects you from an untrusted applet running in
|
|
your browser, use of a SecurityManager while running Tomcat can protect
|
|
your server from trojan servlets, JSPs, JSP beans, and tag libraries.
|
|
Or even inadvertent mistakes.</p>
|
|
|
|
<p>Imagine if someone who is authorized to publish JSPs on your site
|
|
inadvertently included the following in their JSP:</p>
|
|
<div align="left"><table cellspacing="4" cellpadding="0" border="0"><tr><td bgcolor="#023264" width="1" height="1"><img src="./images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td><td bgcolor="#023264" height="1"><img src="./images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td><td bgcolor="#023264" width="1" height="1"><img src="./images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td></tr><tr><td bgcolor="#023264" width="1"><img src="./images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td><td bgcolor="#ffffff" height="1"><pre>
|
|
<% System.exit(1); %>
|
|
</pre></td><td bgcolor="#023264" width="1"><img src="./images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td></tr><tr><td bgcolor="#023264" width="1" height="1"><img src="./images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td><td bgcolor="#023264" height="1"><img src="./images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td><td bgcolor="#023264" width="1" height="1"><img src="./images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td></tr></table></div>
|
|
|
|
<p>Every time this JSP was executed by Tomcat, Tomcat would exit.
|
|
Using the Java SecurityManager is just one more line of defense a
|
|
system administrator can use to keep the server secure and reliable.</p>
|
|
|
|
<p><strong>WARNING</strong> - A security audit
|
|
have been conducted using the Tomcat 5 codebase. Most of the critical
|
|
package have been protected and a new security package protection mechanism
|
|
has been implemented. Still, make sure that you are satisfied with your SecurityManager
|
|
configuration before allowing untrusted users to publish web applications,
|
|
JSPs, servlets, beans, or tag libraries. <strong>However, running with a
|
|
SecurityManager is definitely better than running without one.</strong></p>
|
|
|
|
</blockquote></td></tr></table><table border="0" cellspacing="0" cellpadding="2"><tr><td bgcolor="#525D76"><font color="#ffffff" face="arial,helvetica.sanserif"><a name="Permissions"><strong>Permissions</strong></a></font></td></tr><tr><td><blockquote>
|
|
|
|
<p>Permission classes are used to define what Permissions a class loaded
|
|
by Tomcat will have. There are a number of Permission classes that are
|
|
a standard part of the JDK, and you can create your own Permission class
|
|
for use in your own web applications. Both techniques are used in
|
|
Tomcat 6.</p>
|
|
|
|
|
|
<table border="0" cellspacing="0" cellpadding="2"><tr><td bgcolor="#828DA6"><font color="#ffffff" face="arial,helvetica.sanserif"><a name="Standard Permissions"><strong>Standard Permissions</strong></a></font></td></tr><tr><td><blockquote>
|
|
|
|
<p>This is just a short summary of the standard system SecurityManager
|
|
Permission classes applicable to Tomcat. See
|
|
<a href="http://java.sun.com/security/">http://java.sun.com/security/</a>
|
|
for more information.</p>
|
|
|
|
<ul>
|
|
<li><strong>java.util.PropertyPermission</strong> - Controls read/write
|
|
access to JVM properties such as <code>java.home</code>.</li>
|
|
<li><strong>java.lang.RuntimePermission</strong> - Controls use of
|
|
some System/Runtime functions like <code>exit()</code> and
|
|
<code>exec()</code>. Also control the package access/definition.</li>
|
|
<li><strong>java.io.FilePermission</strong> - Controls read/write/execute
|
|
access to files and directories.</li>
|
|
<li><strong>java.net.SocketPermission</strong> - Controls use of
|
|
network sockets.</li>
|
|
<li><strong>java.net.NetPermission</strong> - Controls use of
|
|
multicast network connections.</li>
|
|
<li><strong>java.lang.reflect.ReflectPermission</strong> - Controls
|
|
use of reflection to do class introspection.</li>
|
|
<li><strong>java.security.SecurityPermission</strong> - Controls access
|
|
to Security methods.</li>
|
|
<li><strong>java.security.AllPermission</strong> - Allows access to all
|
|
permissions, just as if you were running Tomcat without a
|
|
SecurityManager.</li>
|
|
</ul>
|
|
|
|
</blockquote></td></tr></table>
|
|
|
|
|
|
<table border="0" cellspacing="0" cellpadding="2"><tr><td bgcolor="#828DA6"><font color="#ffffff" face="arial,helvetica.sanserif"><a name="Tomcat Custom Permissions"><strong>Tomcat Custom Permissions</strong></a></font></td></tr><tr><td><blockquote>
|
|
|
|
<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>
|
|
<div align="left"><table cellspacing="4" cellpadding="0" border="0"><tr><td bgcolor="#023264" width="1" height="1"><img src="./images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td><td bgcolor="#023264" height="1"><img src="./images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td><td bgcolor="#023264" width="1" height="1"><img src="./images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td></tr><tr><td bgcolor="#023264" width="1"><img src="./images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td><td bgcolor="#ffffff" height="1"><pre>
|
|
permission org.apache.naming.JndiPermission "jndi://localhost/examples/*";
|
|
</pre></td><td bgcolor="#023264" width="1"><img src="./images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td></tr><tr><td bgcolor="#023264" width="1" height="1"><img src="./images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td><td bgcolor="#023264" height="1"><img src="./images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td><td bgcolor="#023264" width="1" height="1"><img src="./images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td></tr></table></div>
|
|
|
|
<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 permission:</p>
|
|
<div align="left"><table cellspacing="4" cellpadding="0" border="0"><tr><td bgcolor="#023264" width="1" height="1"><img src="./images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td><td bgcolor="#023264" height="1"><img src="./images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td><td bgcolor="#023264" width="1" height="1"><img src="./images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td></tr><tr><td bgcolor="#023264" width="1"><img src="./images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td><td bgcolor="#ffffff" height="1"><pre>
|
|
permission java.io.FilePermission "** your application context**", "read";
|
|
</pre></td><td bgcolor="#023264" width="1"><img src="./images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td></tr><tr><td bgcolor="#023264" width="1" height="1"><img src="./images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td><td bgcolor="#023264" height="1"><img src="./images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td><td bgcolor="#023264" width="1" height="1"><img src="./images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td></tr></table></div>
|
|
<p>Where **your application context** equals the folder(or WAR file) under which
|
|
your application has been deployed. </p>
|
|
|
|
</blockquote></td></tr></table>
|
|
|
|
|
|
</blockquote></td></tr></table><table border="0" cellspacing="0" cellpadding="2"><tr><td bgcolor="#525D76"><font color="#ffffff" face="arial,helvetica.sanserif"><a name="Configuring Tomcat With A SecurityManager"><strong>Configuring Tomcat With A SecurityManager</strong></a></font></td></tr><tr><td><blockquote>
|
|
|
|
<h3>Policy File Format</h3>
|
|
|
|
<p>The security policies implemented by the Java SecurityManager are
|
|
configured in the <code>$CATALINA_HOME/conf/catalina.policy</code> file.
|
|
This file completely replaces the <code>java.policy</code> file present
|
|
in your JDK system directories. The <code>catalina.policy</code> file
|
|
can be edited by hand, or you can use the
|
|
<a href="http://java.sun.com/products/jdk/1.2/docs/tooldocs/solaris/policytool.html">policytool</a>
|
|
application that comes with Java 1.2 or later.</p>
|
|
|
|
<p>Entries in the <code>catalina.policy</code> file use the standard
|
|
<code>java.policy</code> file format, as follows:</p>
|
|
<div align="left"><table cellspacing="4" cellpadding="0" border="0"><tr><td bgcolor="#023264" width="1" height="1"><img src="./images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td><td bgcolor="#023264" height="1"><img src="./images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td><td bgcolor="#023264" width="1" height="1"><img src="./images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td></tr><tr><td bgcolor="#023264" width="1"><img src="./images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td><td bgcolor="#ffffff" height="1"><pre>
|
|
// Example policy file entry
|
|
|
|
grant [signedBy <signer>,] [codeBase <code source>] {
|
|
permission <class> [<name> [, <action list>]];
|
|
};
|
|
</pre></td><td bgcolor="#023264" width="1"><img src="./images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td></tr><tr><td bgcolor="#023264" width="1" height="1"><img src="./images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td><td bgcolor="#023264" height="1"><img src="./images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td><td bgcolor="#023264" width="1" height="1"><img src="./images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td></tr></table></div>
|
|
|
|
<p>The <strong>signedBy</strong> and <strong>codeBase</strong> entries are
|
|
optional when granting permissions. Comment lines begin with "//" and
|
|
end at the end of the current line. The <code>codeBase</code> is in the
|
|
form of a URL, and for a file URL can use the <code>${java.home}</code>
|
|
and <code>${catalina.home}</code> properties (which are expanded out to
|
|
the directory paths defined for them by the <code>JAVA_HOME</code> and
|
|
<code>CATALINA_HOME</code> environment variables).</p>
|
|
|
|
<h3>The Default Policy File</h3>
|
|
|
|
<p>The default <code>$CATALINA_HOME/conf/catalina.policy</code> file
|
|
looks like this:</p>
|
|
<div align="left"><table cellspacing="4" cellpadding="0" border="0"><tr><td bgcolor="#023264" width="1" height="1"><img src="./images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td><td bgcolor="#023264" height="1"><img src="./images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td><td bgcolor="#023264" width="1" height="1"><img src="./images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td></tr><tr><td bgcolor="#023264" width="1"><img src="./images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td><td bgcolor="#ffffff" height="1"><pre>
|
|
// ============================================================================
|
|
// catalina.corepolicy - Security Policy Permissions for Tomcat 6
|
|
//
|
|
// This file contains a default set of security policies to be enforced (by the
|
|
// JVM) when Catalina is executed with the "-security" option. In addition
|
|
// to the permissions granted here, the following additional permissions are
|
|
// granted to the codebase specific to each web application:
|
|
//
|
|
// * Read access to the document root directory
|
|
//
|
|
// $Id: security-manager-howto.xml 467215 2006-10-24 03:12:55Z markt $
|
|
// ============================================================================
|
|
|
|
|
|
// ========== SYSTEM CODE PERMISSIONS =========================================
|
|
|
|
|
|
// These permissions apply to javac
|
|
grant codeBase "file:${java.home}/lib/-" {
|
|
permission java.security.AllPermission;
|
|
};
|
|
|
|
// These permissions apply to all shared system extensions
|
|
grant codeBase "file:${java.home}/jre/lib/ext/-" {
|
|
permission java.security.AllPermission;
|
|
};
|
|
|
|
// These permissions apply to javac when ${java.home] points at $JAVA_HOME/jre
|
|
grant codeBase "file:${java.home}/../lib/-" {
|
|
permission java.security.AllPermission;
|
|
};
|
|
|
|
// These permissions apply to all shared system extensions when
|
|
// ${java.home} points at $JAVA_HOME/jre
|
|
grant codeBase "file:${java.home}/lib/ext/-" {
|
|
permission java.security.AllPermission;
|
|
};
|
|
|
|
|
|
// ========== CATALINA CODE PERMISSIONS =======================================
|
|
|
|
|
|
// These permissions apply to the daemon code
|
|
grant codeBase "file:${catalina.home}/bin/commons-daemon.jar" {
|
|
permission java.security.AllPermission;
|
|
};
|
|
|
|
// These permissions apply to the logging API
|
|
grant codeBase "file:${catalina.home}/bin/tomcat-juli.jar" {
|
|
permission java.security.AllPermission;
|
|
};
|
|
|
|
// These permissions apply to the server startup code
|
|
grant codeBase "file:${catalina.home}/bin/bootstrap.jar" {
|
|
permission java.security.AllPermission;
|
|
};
|
|
|
|
// These permissions apply to the servlet API classes
|
|
// and those that are shared across all class loaders
|
|
// located in the "lib" directory
|
|
grant codeBase "file:${catalina.home}/lib/-" {
|
|
permission java.security.AllPermission;
|
|
};
|
|
|
|
|
|
// ========== WEB APPLICATION PERMISSIONS =====================================
|
|
|
|
|
|
// These permissions are granted by default to all web applications
|
|
// In addition, a web application will be given a read FilePermission
|
|
// and JndiPermission for all files and directories in its document root.
|
|
grant {
|
|
// Required for JNDI lookup of named JDBC DataSource's and
|
|
// javamail named MimePart DataSource used to send mail
|
|
permission java.util.PropertyPermission "java.home", "read";
|
|
permission java.util.PropertyPermission "java.naming.*", "read";
|
|
permission java.util.PropertyPermission "javax.sql.*", "read";
|
|
|
|
// OS Specific properties to allow read access
|
|
permission java.util.PropertyPermission "os.name", "read";
|
|
permission java.util.PropertyPermission "os.version", "read";
|
|
permission java.util.PropertyPermission "os.arch", "read";
|
|
permission java.util.PropertyPermission "file.separator", "read";
|
|
permission java.util.PropertyPermission "path.separator", "read";
|
|
permission java.util.PropertyPermission "line.separator", "read";
|
|
|
|
// JVM properties to allow read access
|
|
permission java.util.PropertyPermission "java.version", "read";
|
|
permission java.util.PropertyPermission "java.vendor", "read";
|
|
permission java.util.PropertyPermission "java.vendor.url", "read";
|
|
permission java.util.PropertyPermission "java.class.version", "read";
|
|
permission java.util.PropertyPermission "java.specification.version", "read";
|
|
permission java.util.PropertyPermission "java.specification.vendor", "read";
|
|
permission java.util.PropertyPermission "java.specification.name", "read";
|
|
|
|
permission java.util.PropertyPermission "java.vm.specification.version", "read";
|
|
permission java.util.PropertyPermission "java.vm.specification.vendor", "read";
|
|
permission java.util.PropertyPermission "java.vm.specification.name", "read";
|
|
permission java.util.PropertyPermission "java.vm.version", "read";
|
|
permission java.util.PropertyPermission "java.vm.vendor", "read";
|
|
permission java.util.PropertyPermission "java.vm.name", "read";
|
|
|
|
// Required for OpenJMX
|
|
permission java.lang.RuntimePermission "getAttribute";
|
|
|
|
// Allow read of JAXP compliant XML parser debug
|
|
permission java.util.PropertyPermission "jaxp.debug", "read";
|
|
|
|
// Precompiled JSPs need access to this package.
|
|
permission java.lang.RuntimePermission "accessClassInPackage.org.apache.jasper.runtime";
|
|
permission java.lang.RuntimePermission "accessClassInPackage.org.apache.jasper.runtime.*";
|
|
|
|
};
|
|
|
|
|
|
// You can assign additional permissions to particular web applications by
|
|
// adding additional "grant" entries here, based on the code base for that
|
|
// application, /WEB-INF/classes/, or /WEB-INF/lib/ jar files.
|
|
//
|
|
// Different permissions can be granted to JSP pages, classes loaded from
|
|
// the /WEB-INF/classes/ directory, all jar files in the /WEB-INF/lib/
|
|
// directory, or even to individual jar files in the /WEB-INF/lib/ directory.
|
|
//
|
|
// 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 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";
|
|
// };
|
|
//
|
|
// The permissions granted to the context WEB-INF/classes directory
|
|
// grant codeBase "file:${catalina.home}/webapps/examples/WEB-INF/classes/-" {
|
|
// };
|
|
//
|
|
// The permission granted to your JDBC driver
|
|
// grant codeBase "jar: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:file:${catalina.home}/webapps/examples/WEB-INF/lib/scrape.jar!/-" {
|
|
// permission java.net.SocketPermission "*.noaa.gov:80", "connect";
|
|
// };
|
|
</pre></td><td bgcolor="#023264" width="1"><img src="./images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td></tr><tr><td bgcolor="#023264" width="1" height="1"><img src="./images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td><td bgcolor="#023264" height="1"><img src="./images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td><td bgcolor="#023264" width="1" height="1"><img src="./images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td></tr></table></div>
|
|
|
|
<h3>Starting Tomcat With A SecurityManager</h3>
|
|
|
|
<p>Once you have configured the <code>catalina.policy</code> file for use
|
|
with a SecurityManager, Tomcat can be started with a SecurityManager in
|
|
place by using the "-security" option:</p>
|
|
<div align="left"><table cellspacing="4" cellpadding="0" border="0"><tr><td bgcolor="#023264" width="1" height="1"><img src="./images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td><td bgcolor="#023264" height="1"><img src="./images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td><td bgcolor="#023264" width="1" height="1"><img src="./images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td></tr><tr><td bgcolor="#023264" width="1"><img src="./images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td><td bgcolor="#ffffff" height="1"><pre>
|
|
$CATALINA_HOME/bin/catalina.sh start -security (Unix)
|
|
%CATALINA_HOME%\bin\catalina start -security (Windows)
|
|
</pre></td><td bgcolor="#023264" width="1"><img src="./images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td></tr><tr><td bgcolor="#023264" width="1" height="1"><img src="./images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td><td bgcolor="#023264" height="1"><img src="./images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td><td bgcolor="#023264" width="1" height="1"><img src="./images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td></tr></table></div>
|
|
|
|
</blockquote></td></tr></table><table border="0" cellspacing="0" cellpadding="2"><tr><td bgcolor="#525D76"><font color="#ffffff" face="arial,helvetica.sanserif"><a name="Configuring Package Protection in Tomcat"><strong>Configuring Package Protection in Tomcat</strong></a></font></td></tr><tr><td><blockquote>
|
|
<p>Starting with Tomcat 5, it is now possible to configure which Tomcat
|
|
internal package are protected againts package definition and access. See
|
|
<a href="http://java.sun.com/security/seccodeguide.html">
|
|
http://java.sun.com/security/seccodeguide.html</a>
|
|
for more information.</p>
|
|
|
|
|
|
<p><strong>WARNING</strong>: Be aware that removing the default package protection
|
|
could possibly open a security hole</p>
|
|
|
|
<h3>The Default Properties File</h3>
|
|
|
|
<p>The default <code>$CATALINA_HOME/conf/catalina.properties</code> file
|
|
looks like this:</p>
|
|
<div align="left"><table cellspacing="4" cellpadding="0" border="0"><tr><td bgcolor="#023264" width="1" height="1"><img src="./images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td><td bgcolor="#023264" height="1"><img src="./images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td><td bgcolor="#023264" width="1" height="1"><img src="./images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td></tr><tr><td bgcolor="#023264" width="1"><img src="./images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td><td bgcolor="#ffffff" height="1"><pre>
|
|
#
|
|
# List of comma-separated packages that start with or equal this string
|
|
# will cause a security exception to be thrown when
|
|
# passed to checkPackageAccess unless the
|
|
# corresponding RuntimePermission ("accessClassInPackage."+package) has
|
|
# been granted.
|
|
package.access=sun.,org.apache.catalina.,org.apache.coyote.,org.apache.tomcat.,
|
|
org.apache.jasper.
|
|
#
|
|
# List of comma-separated packages that start with or equal this string
|
|
# will cause a security exception to be thrown when
|
|
# passed to checkPackageDefinition unless the
|
|
# corresponding RuntimePermission ("defineClassInPackage."+package) has
|
|
# been granted.
|
|
#
|
|
# by default, no packages are restricted for definition, and none of
|
|
# the class loaders supplied with the JDK call checkPackageDefinition.
|
|
#
|
|
package.definition=sun.,java.,org.apache.catalina.,org.apache.coyote.,
|
|
org.apache.tomcat.,org.apache.jasper.
|
|
</pre></td><td bgcolor="#023264" width="1"><img src="./images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td></tr><tr><td bgcolor="#023264" width="1" height="1"><img src="./images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td><td bgcolor="#023264" height="1"><img src="./images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td><td bgcolor="#023264" width="1" height="1"><img src="./images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td></tr></table></div>
|
|
<p>Once you have configured the <code>catalina.properties</code> file for use
|
|
with a SecurityManager, remember to re-start Tomcat.</p>
|
|
</blockquote></td></tr></table><table border="0" cellspacing="0" cellpadding="2"><tr><td bgcolor="#525D76"><font color="#ffffff" face="arial,helvetica.sanserif"><a name="Troubleshooting"><strong>Troubleshooting</strong></a></font></td></tr><tr><td><blockquote>
|
|
|
|
<p>If your web application attempts to execute an operation that is
|
|
prohibited by lack of a required Permission, it will throw an
|
|
<code>AccessControLException</code> or a <code>SecurityException</code>
|
|
when the SecurityManager detects the violation. Debugging the permission
|
|
that is missing can be challenging, and one option is to turn on debug
|
|
output of all security decisions that are made during execution. This
|
|
is done by setting a system property before starting Tomcat. The easiest
|
|
way to do this is via the <code>CATALINA_OPTS</code> environment variable.
|
|
Execute this command:</p>
|
|
<div align="left"><table cellspacing="4" cellpadding="0" border="0"><tr><td bgcolor="#023264" width="1" height="1"><img src="./images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td><td bgcolor="#023264" height="1"><img src="./images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td><td bgcolor="#023264" width="1" height="1"><img src="./images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td></tr><tr><td bgcolor="#023264" width="1"><img src="./images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td><td bgcolor="#ffffff" height="1"><pre>
|
|
export CATALINA_OPTS=-Djava.security.debug=all (Unix)
|
|
set CATALINA_OPTS=-Djava.security.debug=all (Windows)
|
|
</pre></td><td bgcolor="#023264" width="1"><img src="./images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td></tr><tr><td bgcolor="#023264" width="1" height="1"><img src="./images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td><td bgcolor="#023264" height="1"><img src="./images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td><td bgcolor="#023264" width="1" height="1"><img src="./images/void.gif" width="1" height="1" vspace="0" hspace="0" border="0"></td></tr></table></div>
|
|
|
|
<p>before starting Tomcat.</p>
|
|
|
|
<p><strong>WARNING</strong> - This will generate <em>many megabytes</em>
|
|
of output! However, it can help you track down problems by searching
|
|
for the word "FAILED" and determining which permission was being checked
|
|
for. See the Java security documentation for more options that you can
|
|
specify here as well.</p>
|
|
|
|
</blockquote></td></tr></table></td></tr><!--FOOTER SEPARATOR--><tr><td colspan="2"><hr noshade="noshade" size="1"></td></tr><!--PAGE FOOTER--><tr><td colspan="2"><div align="center"><font color="#525D76" size="-1"><em>
|
|
Copyright © 1999-2006, Apache Software Foundation
|
|
</em></font></div></td></tr></table></body></html> |