svn commit: r787955 - in /websites/staging/trafficserver/trunk/content/docs/trunk/admin: configuration-files/records.config.en.html security-options/index.en.html

[bu...@apache.org]

Author: buildbot
Date: Mon Apr  4 04:58:06 2011
New Revision: 787955

Log:
Staging update by buildbot

Modified:
    websites/staging/trafficserver/trunk/content/docs/trunk/admin/configuration-files/records.config.en.html
    websites/staging/trafficserver/trunk/content/docs/trunk/admin/security-options/index.en.html

Modified: websites/staging/trafficserver/trunk/content/docs/trunk/admin/configuration-files/records.config.en.html
==============================================================================
--- websites/staging/trafficserver/trunk/content/docs/trunk/admin/configuration-files/records.config.en.html (original)
+++ websites/staging/trafficserver/trunk/content/docs/trunk/admin/configuration-files/records.config.en.html Mon Apr  4 04:58:06 2011
@@ -251,30 +251,6 @@ the <code>records.config</code> file.</p
 </dl>
 <p>keep.</p>
 <dl>
-<dt><em><code>proxy.config.admin.admin_password</code></em></dt>
-<dd><code>STRING</code></dd>
-<dd>Specifies the encrypted administrator password that controls access</dd>
-</dl>
-<p>to Traffic Manager. The format can be recreated with:</p>
-<table class="codehilitetable"><tr><td class="linenos"><div class="linenodiv"><pre>1
-2
-3
-4
-5</pre></div></td><td class="code"><div class="codehilite"><pre><span class="x">#!/usr/bin/php</span>
-<span class="cp">&lt;?php</span>
-    <span class="nv">$foo</span> <span class="o">=</span> <span class="nb">md5</span><span class="p">(</span><span class="s1">&#39;admin&#39;</span><span class="p">,</span><span class="k">true</span><span class="p">);</span>
-    <span class="k">echo</span> <span class="nb">strtoupper</span><span class="p">(</span><span class="nb">substr</span><span class="p">(</span><span class="nb">bin2hex</span><span class="p">(</span><span class="nv">$foo</span><span class="p">),</span><span class="mi">0</span><span class="p">,</span><span class="mi">23</span><span class="p">))</span> <span class="o">.</span> <span class="s2">&quot;</span><span class="se">\n</span><span class="s2">&quot;</span><span class="p">;</span>
-<span class="cp">?&gt;</span><span class="x"></span>
-</pre></div>
-</td></tr></table>
-
-<p>or</p>
-<div class="codehilite"><pre>
-</pre></div>
-
-
-<p>Note that the web interface is not being maintained.</p>
-<dl>
 <dt><em><code>proxy.config.admin.user_id</code></em></dt>
 <dd><code>STRING</code></dd>
 <dd><code>nobody</code></dd>

Modified: websites/staging/trafficserver/trunk/content/docs/trunk/admin/security-options/index.en.html
==============================================================================
--- websites/staging/trafficserver/trunk/content/docs/trunk/admin/security-options/index.en.html (original)
+++ websites/staging/trafficserver/trunk/content/docs/trunk/admin/security-options/index.en.html Mon Apr  4 04:58:06 2011
@@ -44,7 +44,6 @@
 <p>This chapter discusses the following topics: </p>
 <ul>
 <li><a href="#ControllingClientAccessProxyCache">Controlling Client Access to the Proxy Cache</a></li>
-<li><a href="#ControllingAccessTrafficManager">Controlling Access: SSL</a></li>
 <li><a href="#ConfiguringDNSServerSelectionSplit">Configuring DNS Server Selection (Split DNS)</a></li>
 <li><a href="#ConfiguringProxyAuthentication">Configuring Proxy Authentication</a></li>
 <li><a href="#UsingSSLTermination">Using SSL Termination</a></li>
@@ -60,47 +59,6 @@ cache by editing a configuration file.</
 <li>Navigate to the Traffic Server <code>bin</code> directory.</li>
 <li>Run the command <code>traffic_line -x</code> to apply the configuration changes.</li>
 </ol>
-<h2 id="ControllingAccessviaSSL">Controlling Access via SSL</h2>
-<p>By restricting access to Traffic Server, you ensure that only authenticated 
-users can change configuration options and view network traffic statistics. </p>
-<h3 id="UsingSSLforSecureAdministration">Using SSL for Secure Administration</h3>
-<p>Traffic Server supports the Secure Sockets Layer (<strong>SSL</strong>) protocol to provide 
-protection for remote administrative monitoring and configuration. SSL security 
-provides authentication for both ends of a network connection via certificates 
-and provides privacy via encryption. </p>
-<p>To use SSL, you must do the following: </p>
-<ul>
-<li>Obtain an SSL certificate </li>
-<li>Enable SSL </li>
-</ul>
-<h4 id="ObtainanSSLCertificate">Obtain an SSL Certificate</h4>
-<p>The SSL certificate is a text file you must install in the Traffic Server <code>config</code> 
-directory. Either rename the certificate to the default filename <code>private_key.pem</code>, 
-or specify the name of the certificate in the configuration file (follow the 
-procedure in <a href="#EnablingSSL">Enabling SSL</a>). </p>
-<h4 id="EnableSSL">Enable SSL</h4>
-<p>After you've obtained an SSL certificate, enable SSL by manually editing a 
-configuration file. Follow the steps below:</p>
-<ol>
-<li>In a text editor, open the <code>records.config</code> file located in the Traffic Server <code>config</code> directory. </li>
-<li>Edit the following variables:</li>
-<li>
-<dl>
-<dt><strong>Variable</strong> <strong>Description</strong></dt>
-<dt><code>_proxy.config.admin.use_ssl_</code></dt>
-<dd>Set this variable to <code>1</code> to enable SSL.</dd>
-<dt><code>_proxy.config.admin.ssl_cert_file_</code></dt>
-<dd>Set this variable to specify the filename of the SSL certificate. You have 
-    to change the filename only if the certificate file does not use the default 
-    name <code>private_key.pem</code>.</dd>
-</dl>
-</li>
-<li>
-<p>Save and close the <code>records.config</code> file. </p>
-</li>
-<li>Navigate to the Traffic Server <code>bin</code> directory.</li>
-<li>Run the command <code>traffic_line -x</code> to apply the configuration changes.</li>
-</ol>
 <h2 id="configuring_dns_server_selection_split_dns__configuringdnsserverselectionsplitdns">Configuring DNS Server Selection (Split DNS) ## {#ConfiguringDNSServerSelection(SplitDNS)}</h2>
 <p>The <strong>Split DNS </strong>option enables you to configure Traffic Server to use multiple 
 DNS servers, as dictated by your security requirements. For example, you might