You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by KathyM <wy...@aim.com> on 2009/10/26 16:48:59 UTC
certificate verify failed
On one windows client and one netbsd client against two different projects we get the following error:
svn ls https://server/path
svn: OPTIONS of 'https://server/path': SSL handshake failed: SSL error: certificate verify failed (https://server)
These projects on two different servers work fine with all other clients. We use netbsd, windows, mac os, and various others. The servers are netbsd.
Basically, instead of providing the usual dialog asking if we want to accept/reject/accept permanently the "untrusted" certificat, it just fails. We can work around it be installing the cert on the client, but we shouldn't have to.
In the case of the netbsd client, I can find nothing different from any other system. I've checked time stamps. I've checked config files, server files, versions of svn, neon, and openssl. Everything seems identical as it should be with other systems.
I'd like to figure out what the real issue is before it comes up again.
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2411445
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
RE: certificate verify failed
Posted by KathyM <wy...@aim.com>.
svn, version 1.6.5 (r38866)
compiled Oct 2 2009, 11:08:00
OpenSSL 0.9.9-dev 09 May 2008
> On one windows client and one netbsd client against two different projects we get the following error:
>
> svn ls https://server/path
> svn: OPTIONS of 'https://server/path': SSL handshake failed: SSL error: certificate verify failed (https://server)
>
> These projects on two different servers work fine with all other clients. We use netbsd, windows, mac os, and various others. The servers are netbsd.
>
> Basically, instead of providing the usual dialog asking if we want to accept/reject/accept permanently the "untrusted" certificat, it just fails. We can work around it be installing the cert on the client, but we shouldn't have to.
>
> In the case of the netbsd client, I can find nothing different from any other system. I've checked time stamps. I've checked config files, server files, versions of svn, neon, and openssl. Everything seems identical as it should be with other systems.
>
> I'd like to figure out what the real issue is before it comes up again.
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2411446
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].