[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [PATCH] Upgrade svn to use neon 0.19.2 & fix #625

From: Blair Zajac <blair_at_orcaware.com>
Date: 2002-02-20 07:51:52 CET

Ben Collins-Sussman wrote:
> Blair Zajac <blair@orcaware.com> writes:
> > If we get a bad cert, then we can ask if the user wants to abort for
> > the connection, accept the certificate for this one time, or accept
> > it forever. If the cert if accepted forever, then we can save it
> > and use it compare against the server cert next time we connect to
> > it. If they differ then, then we also print a large warning.
> >
> > Where would the server cert would be saved though?
> In the same place we save the username and password: in .svn/auth/, no?

This looks like the right way to go, but a fair amount of work. How about
the patch be applied as is and we can add the cert checking code later.


Blair Zajac <blair@orcaware.com>
Web and OS performance plots - http://www.orcaware.com/orca/
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:37:09 2006

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.