Issue 131 in svnbook: --trust-server-cert analogue for hostname mistmatch

[svnbook at googlecode.com]

Status: New
Owner: ----
Labels: Type-Enhancement Priority-Medium

New issue 131 by pipping.... at googlemail.com: --trust-server-cert analogue  
for hostname mistmatch
http://code.google.com/p/svnbook/issues/detail?id=131

Hello,

some hosts will prompt subversion to complain:

  - The certificate is not issued by a trusted authority. Use the
    fingerprint to validate the certificate manually!

This can be surpressed by calling svn with --trust-server-cert (which  
requires --non-interactive). There is also another thing subversion might  
complain about, though:

   - The certificate hostname does not match.

To my knowledge, there is no flag that makes subversion ignore this problem  
and continue. If this is true, as a consequence, repositories that yield  
such problems cannot be accessed by a non-interactive subversion client!  
(there are horrible workarounds which call `echo t` or `echo p` and pipe  
that to an interactive subversion client of course).

Maybe you can shed some light on the matter. :)