FAQ Patch (was Re: SSH Credential Caching)

On 2004.08.09 20:25:37 +0000, Ben Collins-Sussman wrote:
> On Mon, 2004-08-09 at 19:57, Preston Lee wrote:
> > I've set up an SVN repository and am using SVN+SSH rather than a single
> > svnserve daemon or httpd mod. Whenever I perform client actions on a
> > separate box (example: `svn list svn+ssh://server/path') I am prompted
> > for a password and receive the expected response. However, the
> > credentials I supply are not cached anywhere under ~/.subversion/auth/.
> >
> > I'm guessing this is because the svn binary is really only calling ssh
> > as a child process, and ssh is what is prompting for the password, not
> > the svn client. Is this correct? What is the "correct" way of caching
> > credentials in such a scenario?

> You are correct. And you're like the 10th person to ask this question
> this week. Anyone wanna write a new patch for our FAQ? :-)

Okay.

Log:
Add a FAQ entry for (lack of) svn+ssh authorization caching

* www/project_faq.html
  (change-log-msg): New question and answer.

Index: www/project_faq.html
===================================================================
--- www/project_faq.html (revision 10562)
+++ www/project_faq.html (working copy)
@@ -78,6 +78,10 @@
 <li><a href="#ignore-commit">I have a file in my project that every
 developer must change, but I don't want those local mods to ever be
 committed. How can I make 'svn commit' ignore the file?</a></li>
+<li><a href="#ssh-auth-cache">When I access a repository using
+svn+ssh, my password is not cached in ~/.subversion/auth/. How do
+I avoid having to type it so often?</a></li>
+</a></li>

 <p>
 <strong>Troubleshooting:</strong>
@@ -1276,7 +1280,22 @@
 to its parent directory's svn:ignore property, so it doesn't show up
 as '?' in the 'svn status' command.</p>

+<![CDATA[=========================================================]]>

+<li><a name="ssh-auth-cache">When I access a repository using
+svn+ssh, my password is not cached in ~/.subversion/auth/. How do
+I avoid having to type it so often?</a></li>
+
+<p>ssh has its own scheme for caching authentication tokens. It
+works for the passphrases on ssh keys, not for OS-level passwords,
+so you'll need to do some public key setup.</p>
+
+<p>OpenSSH includes ssh-keygen to create the keys, ssh-agent to
+cache passphrases, and ssh-add to add passphrases to the cache.
+keychain is a popular helper script to simplify using ssh-agent.
+PuTTY, a popular alternative ssh client for Windows, comes with
+PuTTYgen to import OpenSSH keys and pageant to cache passphrases.</p>
+
 <![CDATA[=========================================================]]>

 <p>

-- 
David Ripton    dripton@ripton.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org