Fingerprint: 96:b3:fa:19:bd:4a:ec:c2:bc::b:2a:0a::07:d0 Distinguished name: (c) 2009 Entrust, Inc., is incorporated by reference, Entrust, Inc., US Do you want to proceed?
Accept permanently | Accept once | Reject to be related to Tortoise SVN and not the certificate, which checks out fine at Web and I would say that the cause of the error you list above is because the Entrust certificate is simply not listed in the SSL certificates that Tortoise SVN will trust.
adult singles dating rhine georgia - Tortoise svn error validating server certificate
It is possible to configure your Subversion client to ignore such warnings, but I don't think that is a very good idea.
However, since you say that your Entrust certificate checks out fine, then you can configure your svn client to accept the Entrust cert.
Use the fingerprint to validate the certificate manually! - Valid: from Wed, GMT until Thu, GMT - Issuer: ... (R)eject, accept (t)emporarily or accept (p)ermanently?
SSLVerify Client require SSLVerify Depth 1 SSLOptions Fake Basic Auth DAV svn SVNParent Path "e:/....." Auth Name "Subversion Repositories" Auth Type Basic #Require valid-user Auth User File "C:/......." Authz SVNAccess File "........" I can still successfully browse the repository using plain old https://server:448/svn/... I now commented out SSLVerify Client, SSLVerify Depth, SSLOptions, restarted Apache, and can browse successfully.
Certificate information: - Hostname: svn.- Valid: from Fri, GMT until Mon, GMT - Issuer: ANISSUER, DE - Fingerprint: 37:7d:6a:a7:e9:4c::fe::ab:bb:71:6c::4d:72:0d A friend (who was too lazy to write the answer here) hinted me that the root certificates in Mac OSX are stored in the keychain and suggested two different ways around the problem.
In order to make openssl library (used by svn) to locate them, you need to manually export them and store them in .Well it fooled me for a while, hope it helps someone else.SVN is smart enough to infer that you didn't actually bother verifying that the fingerprint matches. But in all seriousness, https://sourceforge.net/apps/trac/sourceforge/wiki/Subversion#Server Certificate Verification Failed notes that you should open the project url in a trusted browser to check you're not being MITM'ed (should work for non-sourceforge too), e.g.I also changed the port back to 443 and still browsed successfully.So there must be something up with the client-cert auth....Anyway, i did not try with certificates and accepted a crypted password solution, but it could work with certificate, as the fact of changing of port may eliminate the need for "renegotiation".