svn and scripted auth

Hi,

i'm thinking about scripting the subversion client, and specifically
driving an update from a superuser context.

What is not easy to properly understand is how authentication happens
for different svn server types. For a file:/// server, a simple seteguid/seteuid
is enough. For the http:// and https:// scenarios, I can use the
--username/--password
options. How do I go about this in the svn+ssh:// case? Many people use
a pubkey or ssh-agent setup here. Is there a way to control this properly?
In which cases does svn try to do auth at all (http/https?), and in which
does it entirely rely on the underlying layers (ssh+file?). And is it feasible
in all cases to control this from a sudo context?

Maybe this is really covered somwhere in the documentation, but I can't
find it in the SVN Book. Is there authoritative disucssion about this
publickally
available?

Flo

-- 
Florian Ebeling
florian.ebeling@gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org