Ask Different is a question and answer site for power users of Apple hardware and software. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm using Terminal and committing some data to a remote SVN server... every time I get the same message about a new certificate, and I choose to "permanently" accept the cert and it works. However, the next time I commit... same thing. Why isn't the cert being remembered, and how can I fix this?

flat:smarty e$ svn commit ./ -m commit

Error validating server certificate for '':
 - The certificate is not issued by a trusted authority. Use the
   fingerprint to validate the certificate manually!

Certificate information:
 - Hostname: *
 - Valid: from Mon, 11 Jul 2011 00:00:00 GMT until Fri, 07 Sep 2012 12:00:00 GMT
 - Issuer:, DigiCert Inc, US
 - Fingerprint: 3f:97:e9:1f:5c:3e:a9:fb:86:5d:4e:ed:6c:9a:1f:63:a4:f8:25:0a
(R)eject, accept (t)emporarily or accept (p)ermanently? p

Committed revision 19.
share|improve this question
up vote 6 down vote accepted

This doesn't sound like a Terminal problem, but a subversion and/or permissions problem. Did it work at one point in the past, or has it always been a problem?

Most likely the issue is somewhere inside of ~/.subversion/auth/. You could try blowing away the directory, though that will require you to recreate all your credentials. (Maybe something in there is borking up authentication process.)

I suggest you try to recreate your problem with another user profile, computer, or operating system, and compare ~/.subversion directories with your broken system.

If you are convinced its the Terminal's fault, you can try iTerm2, though I expect the same results in the same environment. Good luck!

share|improve this answer
Erasing ~/.subversion completely did the job-- thanks. best, E – Eric Oct 21 '11 at 16:41

I've had the same issue, all files in ~/.subversion/auth/svn.ssl.server/ were set to read-only.

Running chmod u+w ~/.subversion/auth/svn.ssl.server/* fixed it.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.