title: bypass ssl certificate validation in subversion
body: <p>I'm managing a subversion-based build system and we use a self-signed ssl for the server. So from time to time, we get build failures because a new machine has been added and it can't checkout since it's the first time for that machine to contact the svn server. </p>
  
  <p>The error message is like:</p>
  
  <pre><code>icasimpan ~$ svn ls https://scm.myserver.com/trunk
  Error validating server certificate for 'https://scm.myserver.com:443':
   - The certificate is not issued by a trusted authority. Use the
     fingerprint to validate the certificate manually!
  Certificate information:
   - Hostname: scm.myserver.com
   - Valid: from Mon, 05 Dec 2011 00:00:00 GMT until Tue, 11 Dec 2012 23:59:59 GMT
   - Issuer: Terms of use at https://www.verisign.com/rpa (c)10, VeriSign Trust Network, VeriSign, Inc., US
   - Fingerprint: c0:69:f6:67:8d:1f:d2:85:c1:94:9f:59:8e:81:cc:81:3d:1e:44:28
  (R)eject, accept (t)emporarily or accept (p)ermanently? 
  </code></pre>
  
  <p>What I typically need is something like --insecure parameter to curl. Right now, our workaround is to just do some simple svn command so that we could answer "permanently" to and the issue would be solved...at least until the ssl certificate gets changed/renewed again or the build is done on another new machine.</p>
  
  <p>Has someone solved this issue?</p>
  
  <p>Thanks in advance :)</p>