Author: stsp Date: Mon Jun 25 18:25:14 2012 New Revision: 1353694 URL: http://svn.apache.org/viewvc?rev=1353694&view=rev Log: * site/publish/faq.html: Explain a possible reason why 'svn' might fail to permanently store an SSL certificate.
Patch by: Jeyanthan <[email protected]> Modified: subversion/site/publish/faq.html Modified: subversion/site/publish/faq.html URL: http://svn.apache.org/viewvc/subversion/site/publish/faq.html?rev=1353694&r1=1353693&r2=1353694&view=diff ============================================================================== --- subversion/site/publish/faq.html (original) +++ subversion/site/publish/faq.html Mon Jun 25 18:25:14 2012 @@ -266,6 +266,8 @@ a <tt>file:</tt> URL?</a></li> <li><a href="#ssl-error-336032856">When performing Subversion operations over SSL, I get the error <tt>SSL handshake failed: SSL error code -1/1/336032856</a></tt> +<li><a href="#error-validating-server-certificate">I get <tt>Error +validating server certificate</tt> error even though SSL certificates are correctly on the server-side</a></li> <li><a href="#where-are-the-files">After importing files to my repository, I don't see them in the repository directory. Where are they?</a></tt> </a></li> @@ -4188,6 +4190,30 @@ See <a href="http://svn.haxx.se/dev/arch </div> +<div class="h3" id="error-validating-server-certificate"> +<h3>I get <tt>"Error validating server +certificate"</tt> error even though I configure the SSL certificates +correctly in the server. <a class="sectionlink" href="faq.html#error-validating-server-certificate" title="Link to this section">¶</a> +</h3> +<p>This error occurs if the + certificate issuer is not recognized as 'Trusted' +by the SVN client. Subversion will ask you whether you trust the certificate and if you want to store this certificate.<br /> +</p><br> +<pre style="margin-left: 40px;">$ svn info https://mysite.com/svn/repo<br />Error validating server certificate for 'https://mysite.com:443':<br />- The certificate is not issued by a trusted authority. Use the<br />fingerprint to validate the certificate manually!<br />Certificate information:<br />- Hostname: mysite.com<br />- Valid: from Wed, 18 Jan 2012 00:00:00 GMT until Fri, 18 Jan 2013<br />23:59:59 GMT<br />- Issuer: Google Inc, US<br />- Fingerprint:<br />34:4b:90:e7:e3:36:81:0d:53:1f:10:c0:4c:98:66:90:4a:9e:05:c9<br />(R)eject, accept (t)emporarily or accept (p)ermanently?</pre> +<br> +<p>In some cases, even if you accept this by entering 'p' option, the +next time you access SVN, the same error appears again. There can +be reasons. The problem may be your ~/.subversion directory 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.<br /> +</p> +<p>This can be solved by either fixing the permissions with chmod 644 in +<pre style="margin-left: 40px;">~/.subversion/auth/svn.ssl.server</pre> directory or by deleting the directory contents. + If deleted, it gets populated automatically the next time you access.</p> +</div> + + <div class="h3" id="where-are-the-files"> <h3>After importing files to my repository,
