[svnbook] r5683 committed - branches/1.8/zh/book/ ch06-server-configuration.xml

[wuzhouhui at users.sourceforge.net]

Revision: 5683
          http://sourceforge.net/p/svnbook/source/5683
Author:   wuzhouhui
Date:     2018-05-15 12:46:59 +0000 (Tue, 15 May 2018)
Log Message:
-----------
1.8/zh: translation of chapter 6 in progress

Modified Paths:
--------------
    branches/1.8/zh/book/ch06-server-configuration.xml

Modified: branches/1.8/zh/book/ch06-server-configuration.xml
===================================================================
--- branches/1.8/zh/book/ch06-server-configuration.xml	2018-05-13 02:07:24 UTC (rev 5682)
+++ branches/1.8/zh/book/ch06-server-configuration.xml	2018-05-15 12:46:59 UTC (rev 5683)
@@ -1606,6 +1606,7 @@
         </listitem>
       </itemizedlist>
 
+      <!--
       <para>The <command>svnserve</command> server, by default, knows
         only how to send a CRAM-MD5<footnote><para>See RFC
         2195.</para></footnote> authentication challenge.  In essence,
@@ -1616,7 +1617,15 @@
         the stored password to verify that the result is identical.
         <emphasis>At no point does the actual password travel over the
         network.</emphasis></para>
+      -->
+    <para>默认情况下, <command>svnserve</command> 只知道如何发送一个
+      CRAM-MD5<footnote><para>见 RFC 2195.</para></footnote> 授权请求,
+      在本质上, 就是服务器向客户端发送了一小段数据. 客户端使用 MD5 散列算法
+      为数据和密码的混合物创建指纹, 然后发送该指纹, 作为认证请求的响应. 服
+      务器对存放在本地的密码进行同样的计算, 以验证它们是否相同. <emphasis>在
+        任何情况下都会在网络上传输明文密码</emphasis>.</para>
 
+      <!--
       <para>If your <command>svnserve</command> server was built with
         SASL support, it not only knows how to send CRAM-MD5 challenges,
         but also likely knows a whole host of other authentication
@@ -1624,7 +1633,13 @@
         linkend="svn.serverconfig.svnserve.sasl"/> later in this
         chapter to learn how to configure SASL authentication and
         encryption.</para>
+      -->
+      <para>如果 <command>svnserve</command> 支持 SASL, 除了知道如何发送
+        CRAM-MD5 请求外, <command>svnserve</command> 还能使用其他几种认证
+        机制, 本章后面的 <xref linkend="svn.serverconfig.svnserve.sasl"/>
+        将会介绍如何配置 SASL 认证和加密.</para>
 
+      <!--
       <para>It's also possible, of course, for the client to be
         externally authenticated via a tunnel agent, such as
         <command>ssh</command>.  In that case, the server simply
@@ -1632,6 +1647,11 @@
         authenticated username.  For more on this, see the later
         section, <xref
         linkend="svn.serverconfig.svnserve.sshauth"/>.</para>
+      -->
+    <para>当然, 客户端也可以通过一个隧道代理 (例如 <command>ssh</command>),
+      实现外部认证. 在这种情况下, 服务器只是简单地检查自己的用户身份, 然后
+      使用该用户名作为已认证的用户. 更多的相关内容, 见
+      <xref linkend="svn.serverconfig.svnserve.sshauth"/>.</para>
 
       <para>As you've already guessed, a repository's
         <filename>svnserve.conf</filename> file is the central