On Tue, 14 Jan 2003, Sander Striker wrote:
> > From: rbb@rkbloom.net [mailto:rbb@rkbloom.net]
> > Sent: Tuesday, January 14, 2003 10:48 PM
>
> [...]
> >> Well, then why don't we go for that immediately? Drop all this
> >> auth-cache vs. no-auth-cache thing, and write svn-agent daemon. Then we
> >> truly don't have to keep anything on disk. Of course, it does make
> >> client configuration a bit harder, but hey.
> >
> > Because you still need the auth-cache stuff. :-) For the most common
> > case for subversion, you will have people setting up subversion for public
> > consumption, which means that not everybody will be able to use
> > client-side certs for authentication. It also means that not all
> > subversion servers will be run over SSL.
>
> You're missing the point. Use svn-agent for all auth info, regardless
> whether you are doing basic auth or you need a pass for your cert.
Ahhhhh..... The light shines. Yes, you are right, I did miss the point.
> > Yeah, client side config is even harder, because there are a lot of
> > options, but I can't find a way to get rid of any of them.
>
> Actually, I think it becomes easier... No svn-agent == no caching.
> And a running svn-agent == caching. Now svn-agent could have config
> options like expiry of cache etc, but hey... ;) :)
Okay, you two convinced me 110%. I will create an ssh-agent-like
application for svn. Then, once that is done, I will post a patch to
remove all auth caching from subversion. This has a couple of massive
advantages, not the least of which being removing some complexity from
svn. (Also, if I write it correctly, it will be able to support both svn
and ssh, and it will work on Windows!)
Ryan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jan 14 22:43:36 2003