Re: [Issue 650] Changed - certificate handling

On Tue, Apr 09, 2002 at 10:37:41PM +0200, Peter Mathiasson wrote:
> On Tue, Apr 09, 2002 at 11:20:57AM -0400, Greg Hudson wrote:
>...
> > Eh? This is not ssh. Either a certificate is signed by a chain leading
> > to a trusted CA or it's not.

Right. If it is a trusted CA, then caching isn't necessary. If the root CA
is untrusted, then you may still want to trust the cert, so you cache the
fingerprint.

> > I suppose you could cache self-signed certificates so that you'd know if
> > you're getting the same one each time, but certificates do expire, so
> > that's not especially valuble.

Yup, but when a cert expires, then you can requery whether the person wants
to trust it, then cache the new cert/fingerprint.

> I use self-signed certificates, and send them to thoose who need them
> through a trusted channel; phone or gpg signed email.

I expect this will be used a *lot* in development environments. Trust chains
are very different within a dev group, than when you're talking aobut the
Internet as a whole.

> Saving certificate fingerprints, or even whole certificates is a must.
> There should also be a way to pre-install certificates prior to the
> first use.

Yes.

> I'm not saying this is an important issue for the time being, but
> sometime in the future it should be implemented.

I have marked issue 650 as "beta". It is arguably a biggish feature to
implement and could thus be flagged "alpha", but there is no way we could
call ourselves beta without it.

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org