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

wuzhouhui at users.sourceforge.net wuzhouhui at users.sourceforge.net
Thu Jun 7 09:11:44 CDT 2018


Revision: 5711
          http://sourceforge.net/p/svnbook/source/5711
Author:   wuzhouhui
Date:     2018-06-07 14:11:41 +0000 (Thu, 07 Jun 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-06-04 11:45:39 UTC (rev 5710)
+++ branches/1.8/zh/book/ch06-server-configuration.xml	2018-06-07 14:11:41 UTC (rev 5711)
@@ -2526,6 +2526,7 @@
           认证进行登录. 密码认证将无法工作, 因此下面将要介绍的 SSH 技巧
           全都是在围绕 SSH <filename>authorized_keys</filename> 文件.</para>
 
+      <!--
         <para>If it doesn't already exist, create the
           <filename>authorized_keys</filename> file (on Unix,
           typically <filename>~/.ssh/authorized_keys</filename>).
@@ -2532,6 +2533,11 @@
           Each line in this file describes a public key that is
           allowed to connect.  The lines are typically of the
           form:</para>
+      -->
+        <para>如果 <filename>authorized_keys</filename> 事先不存在, 直接创建
+          即可 (在 Unix 系统中, 它的典型位置是 <filename>~/.ssh/authorized_keys
+          </filename>). 文件的每一行都描述了一个允许连接的公钥, 行的典型样式为:
+        </para>
 
         <informalexample>
           <programlisting>
@@ -2539,11 +2545,16 @@
 </programlisting>
         </informalexample>
 
+      <!--
         <para>The first field describes the type of key, the second
           field is the base64-encoded key itself, and the third field
           is a comment.  However, it's a lesser known fact that the
           entire line can be preceded by a <literal>command</literal>
           field:</para>
+      -->
+        <para>第一列描述密钥的类型, 第二列是 base64 编码的密钥, 第三列是注释.
+          除了这三列, 其实还可以添加一个 <literal>command</literal>
+          字段:</para>
 
         <informalexample>
           <programlisting>
@@ -2551,6 +2562,7 @@
 </programlisting>
         </informalexample>
 
+      <!--
         <para>When the <literal>command</literal> field is set, the
           SSH daemon will run the named program instead of the
           typical tunnel-mode <command>svnserve</command> invocation that the
@@ -2557,6 +2569,12 @@
           Subversion client asks for.  This opens the door to a number
           of server-side tricks.  In the following examples, we
           abbreviate the lines of the file as:</para>
+      -->
+        <para>如果含有 <literal>command</literal> 字段, SSH 守护进程将会执行
+          该字段所指定的程序, 而不是 Subversion 客户端所请求的以隧道模式
+          启动的 <command>svnserve</command>. 这种行为允许我们实现多种服务器
+          端技巧, 在下面的例子里, 我们把 <filename>authorized_keys</filename>
+          的每一行简写为:</para>
 
         <informalexample>
           <programlisting>
@@ -2568,11 +2586,19 @@
 
       <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
       <sect3 id="svn.serverconfig.svnserve.sshtricks.fixedcmd">
+      <!--
         <title>Controlling the invoked command</title>
+      -->
+        <title>控制被调用的命令</title>
 
+      <!--
         <para>Because we can specify the executed server-side command,
           it's easy to name a specific <command>svnserve</command>
           binary to run and to pass it extra arguments:</para>
+      -->
+        <para>因为我们可以指定在服务器端被执行的命令, 所以很容易就能指定
+          一个特殊的 <command>svnserve</command> 程序, 并给它传递额外的参数:
+        </para>
 
         <informalexample>
           <programlisting>




More information about the svnbook-dev mailing list