[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

SSH Credential Caching

From: Preston Lee <plee_at_unicon.net>
Date: 2004-08-10 02:57:41 CEST

I'm new to SVN.. please excuse any n00bishness.

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?

As a temporary workaround I've set up ssh public/private key
authentication between client and server so the ssh child processes do
not prompt for a password, but am not fond of this solution in the long

Both server and client are Fedora Core 1 x86 machines, with a subversion
RPM label version 0.32.1-5 ... sorry, I'm not sure what that translates
to for the pristine sources.



To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Aug 10 02:58:03 2004

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.