Error validating server certificate for tortoisesvn male gold diggers dating

Posted by / 21-Jul-2020 16:17

Error validating server certificate for tortoisesvn

What do I have to do to get Subversion to recognize that the certificate we are using for Mac OS Forge *is* issued by a trusted authority?I want a solution that does not involve every Mac Ports contributor having to see this message and press "p"; I want a solution that does not involve anyone seeing this message at all.Hello, I am running svnserver using apache and Web DAV using HTTPS. The certificate I have installed is a wildcard certifcate (*.odesk.com) issued by an intermediate CA , Comodo: CN = Comodo Class 3 Security Services CA OU = (c)2002 Comodo Limited OU = Terms and Conditions of use: OU = Comodo Trust Network O = Comodo Limited C = GB whose Root CA is GTE Cyber Trust Global Root CN = GTE Cyber Trust Global Root OU = GTE Cyber Trust Solutions, Inc.When Tortoise SVN tries to access my server, I get the warning: Error validating server certificate for https://secure.odesk.com:443 Unknown certificate issuer: Fingerprint: ca:a1:ba:7f:37:... O = GTE Corporation C = US The particular wildcard certificate is accepted by IE, Firefox etc.Do I have to somehow provide Subversion with a bundle of well-known trusted certificates?Mac Ports includes the port curl-ca-bundle which installs a bundle of certs from Mozilla, and is used by the curl port to be able to access https sites. This should cause svn2git to either quit, or print a reassuring message about how it's forging ahead.$ git svn fetch This prints the same message I mentioned before, with a security certificate fingerprint and all, and then an additional line that svn2git doesn't show: "(R)eject, accept (t)emporarily or accept (p)ermanently?

The certificate is signed by Verisign, and I updated the cert as well as the ca/intermediate cert on the server.

- For authorized use only/OU=Veri Sign Trust Network verify return:1depth=1 /C=US/O=Veri Sign, Inc./OU=Veri Sign Trust Network/OU=Terms of use at https:// (c)09/CN=Veri Sign Class 3 Secure Server CA - G2verify return:1 depth=0 [removed]verify return:1 Verify return code: 0 (ok)This is a client issue, and not a server issue, right?

If so, then why didn't it complain when we were using our previous cert?

Now, when I try to update my local repository (using svn command line client in Ubuntu), I get this error (I've replaced our domain with example.com): Error validating server certificate for 'https://svn.example.com:443': - The certificate is not issued by a trusted authority.

Certificate information: - Hostname: *.- Valid: from Thu, GMT until Thu, GMT - Issuer: Terms of use at https:// (c)09, Veri Sign Trust Network, Veri Sign, Inc., US - Fingerprint: [removed](R)eject, accept (t)emporarily or accept (p)ermanently?

error validating server certificate for tortoisesvn-84error validating server certificate for tortoisesvn-33error validating server certificate for tortoisesvn-83

Certificate information: - Hostname: [name of our server] - Valid: from Mon, GMT until Thu, GMT- Issuer: [name of our server] - Fingerprint: 8a::83:4b:1b:c6:8e:1e:9f:85:ab:86:b0:4a:d1:bb:8e:44(R)eject, accept (t)emporarily or accept (p)ermanently? The problem is that, while running a SVN command using the Team City Command Line Runner, I have hit the same error.