svn: OPTIONS of 'https://SERVER_IP/svn/myproject/trunk': Server certificate verification failed: certificate issued for a different hostname, issuer is not trusted (https://SERVER_IP) If the client receives a server certificate, it needs to verify that it trusts the certificate: is the server really who it claims to be?

error validating server certificate for xcode-60error validating server certificate for xcode-64

今天使用Xcode自带的svn客户端时,总是连接不上服务器,报如下错误: Error validating server certificate for ‘https://svn2.assembla.com:443’: – The certificate is not issued by a trusted authority.

Use the fingerprint to validate the certificate manually!

mbp:~ user$ svn co https://svn.mysite.com/svn/testrepo Error validating server certificate for 'https://svn.mysite.com:443': - The certificate is not issued by a trusted authority.

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.

That situation can occur if subversion command is triggered by some process.

In that case you need to find out, what user and group is this process running under.

Then you type your credentials and get to choose if you want to add your certificate permanently.

You say “yes”, but next time get the same silly question. The problem may be, that the subversion configuration directory, which is normally under your has WRONG permissions, so that each time you want to permanently add the credentials, svn actually cannot do so, and also doesn’t inform you that it can’t.

Certificate information: - Hostname: svn.- Valid: from Sun, GMT until Tue, GMT - Issuer: Secure Digital Certificate Signing, Start Com Ltd., IL - Fingerprint: :f6:3c:2d:d5:0f:b9:6e:b2:a0:d3:be:e:b7:7a:0c:26:3b (R)eject, accept (t)emporarily or accept (p)ermanently?