On Mon, 2004-08-09 at 19:57, Preston Lee wrote:
> 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?
>
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? :-)
Subversion isn't doing any authentication at all, so there's no
~/.subversion/auth/ caching going on. The standard recommendation is to
use a tool like 'ssh-agent' on unix or 'pageant' on win32 to cache SSH
passwords in memory. (This is the same thing CVS users use when using
CVS_RSH=ssh)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Aug 10 03:27:33 2004