Error validating server certificate svn
I'm using Terminal and committing some data to a remote SVN server... Why isn't the cert being remembered, and how can I fix this?
every time I get the same message about a new certificate, and I choose to "permanently" accept the cert and it works. flat:smarty e$ svn commit ./ -m commit Error validating server certificate for 'https://x.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.
In order to make openssl library (used by svn) to locate them, you need to manually export them and store them in .
In the above example output I changed various private information to all capital letters to represent what was there including HTTPS-SVN-REPOSITORY-URL-HERE, THE-USERNAME-HERE, THE-PASSWORD-HERE, USERNAME-HERE, and the path to where the repository was being cloned.
This used to work before, but maybe the server has been changed.If a certificate is not trusted by client, the connection will be encrypted but it's not sure that client communicates with the true server.Self-signed SSL certificate is pre-generated during the first setup of Visual SVN Server.However, if the certificate is not trusted subversion will ask you whether you trust the certificate and if you want to add this certifacte.- Valid: from Wed, GMT until Thu, GMT - Issuer: Google Inc, US - Fingerprint: 34:4b:90:e7:e:0d:52:1f:10:c0:4c::4a:9e:05:c9 (R)eject, accept (t)emporarily or accept (p)ermanently?