On Oct 28, 2005, at 21:18, Doyle, Patrick wrote:
> I would like to figure out the easiest way for users to authenticate
> themselves with my Sunversion server the first time (recognizing that,
> subsequent to that first time, the authentication data will have been
> cached).
>
> Right now, I add/edit a property on a file and commit it, but
> that seems a
> little roundabout. Note that I want to preserve the read-only,
> passwordless, access to the repository that I currently enjoy.
Via the svn+ssh protocol, you can set up secure keys so that you
never get asked for a password. This is described in the docs.
Since you're talking about passwords being cached, though, I presume
you're talking about svn or http or https protocol. In these cases,
the passwords can get cached in ~/.subversion/auth/svn.simple. If you
look in one of those files, you'll see that the file format is very
simple. You could probably write those files yourself, if you could
only figure out how to generate the hash that's used for the
filename. I guess a quick trip to the Subversion source code would
reveal how that's put together, or maybe someone here knows off the
top of their head.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Oct 29 16:31:40 2005