Error validating server certificate for google code

13 Sep

Just fire up your SVN site in a browser and check out the certificate path, leading back to the root - make sure that root's thumbprint matches the file that you have.I have faced the annoying problem that for unknown reasons I got a security exception when accessing the subversion repository for one of my Google Code projects.If your website is secured by a certificate with the name will receive this error if you connect using any of the following names: Even though all of the above addresses would get you to a site with a valid certificate, you could still get a name error if you are connecting to a name other than the one that the certificate was issued to.Digi Cert's Multi-Domain (SAN) Certificates were designed to resolve this problem by allowing one certificate to be issued to multiple names (i.e., fully-qualified domain names or IP addresses).And it won't ask you next time to confirm the certificate until its cached.Note that if you have a remote mounted drive it's possible that it can look like you're the owner of the file, if the remote system has the same username.SVN is smart enough to infer that you didn't actually bother verifying that the fingerprint matches. But in all seriousness, 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.

mbp:~ user$ svn co Error validating server certificate for '': - The certificate is not issued by a trusted authority.I have just configured Apache to run HTTPS with an SSL Certificate from Geotrust.The Apache part of things is running fine (I can access my site via HTTPS without warnings or issues).This used to work before, but maybe the server has been changed.However, if the certificate is not trusted subversion will ask you whether you trust the certificate and if you want to add this certifacte.In order to make openssl library (used by svn) to locate them, you need to manually export them and store them in .I am running Red Hat Enterprise Linux 6 and have a subversion server installed (with Apache).The following warnings are presented when you access a website that has a security certificate installed that was issued to a domain other than the you accessed.Internet Explorer: "The security certificate presented by this website was issued for a different website's address." Firefox: " an invalid security certificate." or "The certificate is only valid for the following names:" This happens when the common name to which an SSL Certificate is issued (e.g., doesn't exactly match the name displayed in the URL bar.Use the fingerprint to validate the certificate manually!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.