Hi Stefan,

thanks for the information. That helped a lot - and I didn't have to change 
the hostname only my putty-entries connecting to it which had a 
blank-character in it.
After changing the blank to a underscore like so for example:

"02_kai-h00" instead of "02 kai-h00" the TVSN-URL changed 
from
svn+ssh://svnuser@02%20kai-h00/vufind-1 
to
svn+ssh://svnuser@02_kai-h00/vufind-1
and everything works fine again. But I had to know that the problem was the 
blank in the first place... :-)

So thanks again,
Kate



Am Mittwoch, 25. Oktober 2017 20:08:24 UTC+2 schrieb Stefan:
>
>
>
> On Wednesday, October 25, 2017 at 10:26:09 AM UTC+2, Katharina Wolkwitz 
> wrote:
>>
>> Hello everybody,
>>
>> I've got three servers running on SLES (2 on 12.3 and 1 on 11.3) with SVN 
>> 1.9.7 / 1.7.4 repositories on them.
>> On my Windows 7 64bit PC I've upgraded to TortoiseSVN 1.9.7, Build 27907 
>> - 64 Bit yesterday from 1.9.6 and since then I cannot access the 
>> repositories on any of the servers anymore. I get the following 
>> error-message from repo-browser, update or new-checkout:
>>
>> Unable to connect to a repository at URL
>>  'svn+ssh://svnuser@02%20kai-h00/vufind-1'
>> Invalid host 'svnuser@02%20kai-h00'
>>
>
> I think this is the problem: you have escaped chars in the host name! The 
> host name should not contain escaped chars or chars that need escaping.
> Handling of such hostnames was disabled due to a security problem in 
> earlier svn versions. See
> https://subversion.apache.org/security/CVE-2017-9800-advisory.txt
> for details.
>
> You have to change the hostname to make it work again. Sorry.
>
> Stefan
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"TortoiseSVN" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tortoisesvn/3965e72f-da33-4e22-99e0-3b06cdfff626%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to