[svnbook] r4112 committed - Translation in progress.
svnbook at googlecode.com
svnbook at googlecode.com
Fri Oct 14 07:35:12 CDT 2011
Revision: 4112
Author: jmfelderhoff at gmx.eu
Date: Fri Oct 14 05:34:21 2011
Log: Translation in progress.
http://code.google.com/p/svnbook/source/detail?r=4112
Modified:
/branches/1.5/de/book/ch06-server-configuration.xml
=======================================
--- /branches/1.5/de/book/ch06-server-configuration.xml Thu Oct 13 08:09:04
2011
+++ /branches/1.5/de/book/ch06-server-configuration.xml Fri Oct 14 05:34:21
2011
@@ -2269,8 +2269,12 @@
<!-- ===============================================================
-->
<sect2 id="svn.serverconfig.svnserve.sshauth">
+<!--
<title>Tunneling over SSH</title>
-
+-->
+ <title>Tunneln über SSH</title>
+
+<!--
<para><command>svnserve</command>'s built-in authentication (and
SASL support) can be very handy, because it avoids the need to
create real system accounts. On the other hand, some
@@ -2278,10 +2282,25 @@
authentication frameworks in place. In these situations, all
of the project's users already have system accounts and the
ability to <quote>SSH into</quote> the server machine.</para>
-
+-->
+ <para>Die Eingebaute Authentifizierung (und die
+ SASL-Unterstützung) von <command>svnserve</command> kann sehr
+ praktisch sein, da es die Notwendigkeit echter Systemkonten
+ vermeidet. Andererseits haben einige Administratoren bereits
+ etablierte SSH-Authentifizierungs-Frameworks im Einsatz. In
+ diesen Fällen haben die Benutzer des Projektes bereits
+ Systemkonten, um sich damit über SSH mit dem Server zu
+ verbinden.</para>
+
+<!--
<para>It's easy to use SSH in conjunction with
<command>svnserve</command>. The client simply uses the
<literal>svn+ssh://</literal> URL scheme to connect:</para>
+-->
+ <para>Es ist einfach, SSH in Verbindung mit
+ <command>svnserve</command> zu verwenden. Der Client benutzt
+ zum Verbinden einfach das <literal>svn+ssh://</literal>
+ URL-Schema:</para>
<screen>
$ whoami
@@ -2296,6 +2315,7 @@
…
</screen>
+<!--
<para>In this example, the Subversion client is invoking a local
<command>ssh</command> process, connecting to
<literal>host.example.com</literal>, authenticating as the
@@ -2310,6 +2330,22 @@
If the client performs a commit, the authenticated username
<literal>harryssh</literal> will be used as the author
of the new revision.</para>
+-->
+ <para>In diesem Beispiel ruft der Subversion-Client einen
+ lokalen
+ <command>ssh</command> process, connecting to
+ <literal>host.example.com</literal>, authenticating as the
+ user <literal>harryssh</literal> (according to SSH user
+ configuration), then spawning a private
+ <command>svnserve</command> process on the remote machine
+ running as the user <literal>harryssh</literal>. The
+ <command>svnserve</command> command is being invoked in tunnel
+ mode (<option>-t</option>), and its network protocol is being
+ <quote>tunneled</quote> over the encrypted connection by
+ <command>ssh</command>, the tunnel agent.
+ If the client performs a commit, the authenticated username
+ <literal>harryssh</literal> will be used as the author
+ of the new revision.</para>
<para>The important thing to understand here is that the
Subversion client is <emphasis>not</emphasis> connecting to a
More information about the svnbook-dev
mailing list