/usr/share/doc/subcommander/html/apas01.html is in subcommander-doc 2.0.0~b5p2-5.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 | <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Configuration of svn+ssh</title><meta name="generator" content="DocBook XSL Stylesheets V1.76.1"><link rel="home" href="index.html" title="The Subcommander Guide"><link rel="up" href="apa.html" title="Appendix A. Miscellaneous"><link rel="prev" href="apa.html" title="Appendix A. Miscellaneous"><link rel="next" href="apas02.html" title="Subcommander Website"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Configuration of svn+ssh</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="apa.html">Prev</a> </td><th width="60%" align="center">Appendix A. Miscellaneous</th><td width="20%" align="right"> <a accesskey="n" href="apas02.html">Next</a></td></tr></table><hr></div><div class="section" title="Configuration of svn+ssh"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="misc_svn_ssh"></a>Configuration of svn+ssh<a class="indexterm" name="idm43536"></a></h2></div></div></div><p>The configuration of svn+ssh is not a special subcommander issue but
a subversion one. The configuration is done in subversions own
configuration file. Anyway, the next few sections give a short description
how to configure svn+ssh with public key authentication on the different
plattforms.</p><div class="simplesect" title="Win32"><div class="titlepage"><div><div><h3 class="title"><a name="ssh_win32"></a>Win32<a class="indexterm" name="idp109912"></a></h3></div></div></div><p>The easiest way to run <code class="literal">svn+ssh</code> from
subcommander on Win32 is to use PuTTY for handling the ssh connections.
PuTTY is a free SSH client for Win32. You can download PuTTY from its
web site (see <a class="xref" href="apas06.html" title="PuTTY">the section called “PuTTY”</a>).</p><p>The <code class="literal">ssh</code> part (the scheme) in
<code class="literal">svn+ssh</code> is more or less free configurable. Its an
identifier subversion uses to look up the command it should use to run
the svnserve process on a remote machine. For the example we add the
PuTTY command as the scheme <code class="literal">putty</code> into our local
subversion configuration file. We can then access our repository using
<code class="literal">svn+putty//<server>/<repositorypath></code>. It
doesn't matter if our server url is given as svn+ssh. It is only
important that we can access the server machine with ssh using public
key authentication.</p><p>Here is what we add to the configuration file in the
<code class="literal">tunnels</code> section (this is just one of several possible
ssh configurations we could use):</p><pre class="programlisting">[tunnels]
putty = <path>/plink.exe -ssh -2 -l <username> -i <keypath>/id_rsa.ppk</pre><p>The <code class="literal">plink.exe</code> is PuTTYs command line tool. We
tell it to create an <code class="literal">ssh</code> connection using the ssh
protocol 2 (<code class="literal">-2</code>), our username (<code class="literal">-l</code>)
we want to use to connect to the repository server and the filename
(<code class="literal">-i</code>) of our private key for the ssh
authentication.</p><p>Since our private key is encrypted with a pass phrase, PuTTY would
ask on each call to the repository for the pass phrase to decode our
private key. This would make the secure ssh connection completly
unusable. The solution is another PuTTY tool called
<code class="literal">Pageant</code>.</p><p>Pageant stores decoded private keys at runtime in memory. If Plink
detects that Pageant is running it requests the decoded private key from
it. We only need to load our private into Pageant and enter the pass
phrase (one time) so it can decode it.</p><p>That's all we need to do to use <code class="literal">svn+putty</code>://..
urls to access our subversion repository over a secure ssh connection.
Because we configured this in subversions configuration file,
<code class="literal">svn+putty</code> will work from subcommander and it will
also work with subversions command line tool.</p><div class="sidebar" title="subversion configuration file"><div class="titlepage"><div><div><p class="title"><b>subversion configuration file</b></p></div></div></div><p>Subversions configuration file is at
<code class="literal">%APPDATA%\Subversion\config</code>.
<code class="literal">%APPDATA%</code> is typically something like
<code class="literal">C:\Documents and
Settings\<yourwindowslogin>\Application Data</code>.</p></div></div><div class="simplesect" title="Unix"><div class="titlepage"><div><div><h3 class="title"><a name="idp119576"></a>Unix<a class="indexterm" name="idp119864"></a></h3></div></div></div><p>..todo..</p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="apa.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="apa.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="apas02.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Appendix A. Miscellaneous </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Subcommander Website</td></tr></table></div></body></html>
|