On Wed, Mar 23, 2011 at 9:47 AM, Cecil Westerhof <ce...@decebal.nl> wrote:
> As I understand it the caching or not is done through setting:
> ${HOME}/.subversion/servers
>
> Is it possible to do this centrally?
Your question is a bit unclear. The client needs cached keys, or
passwords, in order to do anything that requires network authorization
on the upstream Subversion server. The Windows clients, such as
TortoiseSVN, have their own encrypted key storage setup. The UNIX and
Linux clients will store HTTP/HTTPS passwords in
$HOME/.subversion/servers, by default, and store them in clear text.
It's possible to use access techniques that do not do this, such as
SSL keys or SSH keys for svn+ssh. That requires the client to have a
private, ideally passphrase protected, and the public keys to be
stored and managed on the server. This is coverd in the Subversion
"red book", though the actual management of the keys is not well
addressed.
Would that cover your needs?
