You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by mg...@apache.org on 2016/12/18 14:26:46 UTC
svn commit: r1774891 - /tomcat/trunk/webapps/docs/security-howto.xml
Author: mgrigorov
Date: Sun Dec 18 14:26:45 2016
New Revision: 1774891
URL: http://svn.apache.org/viewvc?rev=1774891&view=rev
Log:
Fix typos
Modified:
tomcat/trunk/webapps/docs/security-howto.xml
Modified: tomcat/trunk/webapps/docs/security-howto.xml
URL: http://svn.apache.org/viewvc/tomcat/trunk/webapps/docs/security-howto.xml?rev=1774891&r1=1774890&r2=1774891&view=diff
==============================================================================
--- tomcat/trunk/webapps/docs/security-howto.xml (original)
+++ tomcat/trunk/webapps/docs/security-howto.xml Sun Dec 18 14:26:45 2016
@@ -77,12 +77,12 @@
<subsection name="JMX">
<p>The security of the JMX connection is dependent on the implementation
- provided by the JRE and therefore falls outside the control of Tomact.</p>
+ provided by the JRE and therefore falls outside the control of Tomcat.</p>
<p>Typically, access control is very limited (either read-only to
everything or read-write to everything). Tomcat exposes a large amount
of internal information and control via JMX to aid debugging, monitoring
- and management. Give the limited access control available, JMX access
+ and management. Given the limited access control available, JMX access
should be treated as equivalent to local root/admin access and restricted
accordingly.</p>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org