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

Re: Standard for communicating with user?

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2002-11-25 18:26:21 CET

<rbb@apache.org> writes:

> I am basically following the comments in session.c in libsvn_ra_dav.
> Basically, once the SSL cert is received, we check it against a cert file
> in the ~/.svn directory. If the cert is valid, we are good. Otherwise,
> we prompt the user to determine if we should accept the cert for the
> session, forever, or reject it. I think I know how to do all of this, but
> prompting the user was stopping me.

Ah. Are you sure you want to store the cert in .svn?

Right now, libsvn_wc caches username/password info recursively through
a working copy's .svn areas. But for an SSL cert, I wonder if it
makes more sense to store the data in a central place. That's why we
have ~/.subversion/. Or is that what you meant when you wrote ~/.svn? :-)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Nov 25 18:28:37 2002

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.