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

Re: certificate problems and 403 Forbidden for svn 0.25.0

From: Martin v. L÷wis <martin_at_v.loewis.de>
Date: 2003-07-21 06:59:52 CEST

Garret Wilson <garret@globalmentor.com> writes:

> This also requires that I install some CA file on my web server, so
> maybe neon has some problems with this extra CA step---but it works
> fine with every browser I've used.
> So I shouldn't even see the prompts in the first place. What's wrong?

I think you are missing a number of points here. Neon, by itself, does
not trust any CA, neither Comodo Class 3 Security Services CA, nor GTE
Cybertrust. You actively have to *configure* which certificates neon
trust, and you have to do that on the client side.

So you have to save both the Comodo certificate and the GTE
certificate into a PEM file, and list this PEM file as

Alternatively, you can have openssl trust these CAs by default - you
would have to find out where openssl stores it CA certs and verify
that the two certificates are listed there.

What CAs your browsers trust is completely irrelevant.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jul 21 07:01:07 2003

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.