TortoiseSVN 1.7.6, 1.7.7, 1.7.8 and SSL handshake problem

3,177 views
Skip to first unread message

Eric DELAGE

unread,
Aug 28, 2012, 6:08:06 AM8/28/12
to us...@tortoisesvn.tigris.org
Hi,

I read on the web that many people can't connect anymore to their SVN repositories when moving from TortoiseSVN to TortoiseSVN 1.7.7 or 1.7.8.
I also have this problem and I get the following error message:

> Unable to connect to a repository at URL
> OPTIONS of
>  SSL handshake failed: SSL error: cant get key

On the Apache server, in SSL.log, I have:

> ... - - "GET /" 492

When I use AnkhSvn from MS Visual Studio 2010 SP1, it works properly.
When moving back to TortoiseSVN 1.7.6 it works properly again.

I run TortoiseSVN 1.7.8 on Windows 7 Pro with the latest patches.
I run AnkhSvn 2.4.11610.
I run the latest Subversion 1.7.6 mods on an Apache Server.

Any idea what goes wrong? I haven't found any solution about it on internet
but many many people who encounter the same problem.

Stefan Küng

unread,
Aug 28, 2012, 8:11:25 AM8/28/12
to us...@tortoisesvn.tigris.org
http://bit.ly/Rj6r9r

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3001603

To unsubscribe from this discussion, e-mail: [users-un...@tortoisesvn.tigris.org].

Simon Large

unread,
Aug 28, 2012, 8:38:25 AM8/28/12
to us...@tortoisesvn.tigris.org
On 28 August 2012 13:11, Stefan Küng <torto...@gmail.com> wrote:
> On Tue, Aug 28, 2012 at 12:08 PM, Eric DELAGE <eric_...@hotmail.com> wrote:
>> Hi,
>>
>> I read on the web that many people can't connect anymore to their SVN
>> repositories when moving from TortoiseSVN to TortoiseSVN 1.7.7 or 1.7.8.
>> I also have this problem and I get the following error message:
>>
>>> Unable to connect to a repository at URL
>>>
>>> 'https://www.complexeventprocessors.com/Company-Eric/SVNROOT/RD_Projects/Eajks.Webs.Imaging/B-x.x.x-Baseline/Projects'
>>> OPTIONS of
>>>
>>> 'https://www.complexeventprocessors.com/Company-Eric/SVNROOT/RD_Projects/Eajks.Webs.Imaging/B-x.x.x-Baseline/Projects':
>>> SSL handshake failed: SSL error: cant get key
>>> (https://www.complexeventprocessors.com)
>>
>> On the Apache server, in SSL.log, I have:
>>
>>> ... - - "GET /" 492
>>
>> When I use AnkhSvn from MS Visual Studio 2010 SP1, it works properly.
>> When moving back to TortoiseSVN 1.7.6 it works properly again.
>>
>> I run TortoiseSVN 1.7.8 on Windows 7 Pro with the latest patches.
>> I run AnkhSvn 2.4.11610.
>> I run the latest Subversion 1.7.6 mods on an Apache Server.
>>
>> Any idea what goes wrong? I haven't found any solution about it on internet
>> but many many people who encounter the same problem.
>
> http://bit.ly/Rj6r9r

That's a bit harsh, isn't it? He has already googled for solutions and
not found anything, and I don't see any solution in that search
either. It seems a reasonable question since everything was working in
1.7.6 and broke in 1.7.7, meaning it is a client side change rather
than a generic SSL certificate problem.

There is a very similar question here:

http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2969812

The start of that thread gives a possible cause (and possible
workaround in TSVN), and the last message in the thread says that
"Setting the registry key OpenSSLCapi to 0 fixes the problem".

Simon

--
: ___
: oo // \\ "De Chelonian Mobile"
: (_,\/ \_/ \ TortoiseSVN
: \ \_/_\_/> The coolest Interface to (Sub)Version Control
: /_/ \_\ http://tortoisesvn.net

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3001609

Eric DELAGE

unread,
Aug 28, 2012, 12:43:32 PM8/28/12
to us...@tortoisesvn.tigris.org
>>> Any idea what goes wrong? I haven't found any
>>> solution about it on internet but many many people
>>> who encounter the same problem.
>>
>> http://bit.ly/Rj6r9r
>
> That's a bit harsh, isn't it? He has already googled
> for solutions and not found anything, and I don't see
> any solution in that search either. It seems a
> reasonable question since everything was working in
> 1.7.6 and broke in 1.7.7, meaning it is a client side
> change rather than a generic SSL certificate problem.

Moreover upgrading to the latest version of another client - AnkhSvn which has been recently updated for Subversion 1.7.6 - is never an issue. So there was a modification in TortoiseSVN, probably a legitimate and required one, which cause a SSL error message (due perhaps to an Apache/SSL misconfiguration) to appear which perhaps didn't appear before. It would be nice to know what changed in TortoiseSVN 1.7.7 as it would help to discover the root of the problem.

As many of my colleagues/friends, I consider moving from SVN to Hg as they have always had a better support. I consider it a pity because I use SVN in production from the 1.2 version but I can't stay stucked in a bug for 2-3 months now with for only answer "not my problem ; google for SSL" as the SVN repository is unaccessible with the two latest TortoiseSVN releases.

> On 28 August 2012 13:11, Stefan Küng <tortoisesvn at gmail dot com> wrote:
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3001676

Simon Large

unread,
Aug 28, 2012, 4:53:53 PM8/28/12
to us...@tortoisesvn.tigris.org
On 28 August 2012 17:43, Eric DELAGE <Eric_...@hotmail.com> wrote:
> As many of my colleagues/friends, I consider moving from SVN to Hg as they have always had a better support.

I always thought SVN/TSVN support was pretty good, but I don't know Hg.

> I consider it a pity because I use SVN in production from the 1.2 version but I can't stay stucked in a bug for 2-3 months now with for only answer "not my problem ; google for SSL" as the SVN repository is unaccessible with the two latest TortoiseSVN releases.

If you could provide access to the repository, or the URL of a public
repo that shows the same problem then it would be a lot easier to
debug. Without that we can only guess.

Simon

--
: ___
: oo // \\ "De Chelonian Mobile"
: (_,\/ \_/ \ TortoiseSVN
: \ \_/_\_/> The coolest Interface to (Sub)Version Control
: /_/ \_\ http://tortoisesvn.net

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3001716

Oto BREZINA

unread,
Aug 29, 2012, 2:12:54 AM8/29/12
to us...@tortoisesvn.tigris.org
On 2012-08-28 18:43, Eric DELAGE wrote:

> Moreover upgrading to the latest version of another client - AnkhSvn which has been recently updated for Subversion 1.7.6 - is never an issue. So there was a modification in TortoiseSVN, probably a legitimate and required one, which cause a SSL error message (due perhaps to an Apache/SSL misconfiguration) to appear which perhaps didn't appear before. It would be nice to know what changed in TortoiseSVN 1.7.7 as it would help to discover the root of the problem.
>
>
I'm trying get thru logs. Can you help me with some answers (some may be
already answered)?

What OS you use? I guess 64 bit. Have you reported that issue on 32bit
as well?
Are you using neon or sarf? Can you check what versions AnkhSvn uses?

You stated 1.7.6 is working, 1.7.7 and 1.7.8 is not suggesting change
happened between 2012-03-08 r22633 and 2012-05-15 r22909.
Leaving as with 282revs. Only 76 or which happened on 1.7.x branch.

After removing some translation and MSI numbering we are left with about
60 revs.

Hightlights:

r22853
Merged r22846, r22847, r22849 and r22852 from trunk:
* Silence compiler warnings.
* Link with /LTCG
* Add the neon and OpenSSL output paths when linking to fix the LNK4099
warning.
* If the log dialog is started with HEAD, on refresh also change the
start rev to the new HEAD revision. (Fixes issue #222) : log dialog does
not refresh to HEAD.
----

r22661
Merged r22660 from trunk:
* Close SASL *after* SVN has cleaned up all memory and handles. (Fixes
issue #241) : crash when closing app using sasl authentication.
----

r22665
Merged r22663 and r22664 from trunk:
* Check all return values from the encrypting/decrypting APIs and
initialize the variables properly. (Fixes issue #242) : crash when
authenticating.
----

r22679
Merged r22676, r22677 and r22678 from trunk:
* Don't abort on reading the config file.
* Refactor the code to set up the SSH configuration into its own function.
* Check for valid view before trying to select text. (Fixes issue #244)
: Crash with hotkeys in TortoiseMerge.
----

r22710
Update to serf 1.0.3
----
/branches/1.7.x/ext

r22893
Update to svn 1.7.5 and apr 1.4.6
----
/branches/1.7.x/ext



--
Oto ot(ik) BREZINA - 오토

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3001811

Oto BREZINA

unread,
Aug 29, 2012, 2:13:02 AM8/29/12
to us...@tortoisesvn.tigris.org
On 2012-08-28 18:43, Eric DELAGE wrote:

> Moreover upgrading to the latest version of another client - AnkhSvn which has been recently updated for Subversion 1.7.6 - is never an issue. So there was a modification in TortoiseSVN, probably a legitimate and required one, which cause a SSL error message (due perhaps to an Apache/SSL misconfiguration) to appear which perhaps didn't appear before. It would be nice to know what changed in TortoiseSVN 1.7.7 as it would help to discover the root of the problem.
>
>
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3001812

Eric DELAGE

unread,
Aug 29, 2012, 5:23:02 AM8/29/12
to us...@tortoisesvn.tigris.org
Hi

Unfortunately, I can't give you any kind of access to the repository.

This morning I discover something which may help. Using the same Apache/SSL/Subversion-1.7.6 setup and the same TortoiseSVN-1.7.7-8/SSL certificate on a Windows 7 Pro 64b and a Windows Vista Home 32b, I get different results. It works on Vista. It doesn't work on 7.

> On 28 August 2012 17:43, Eric DELAGE <Eric_DELAGE at hotmail dot com> wrote:
> > As many of my colleagues/friends, I consider moving from SVN to Hg as they have always had a better support.
>
> I always thought SVN/TSVN support was pretty good, but I don't know Hg.
>
> > I consider it a pity because I use SVN in production from the 1.2 version but I can't stay stucked in a bug for 2-3 months now with for only answer "not my problem ; google for SSL" as the SVN repository is unaccessible with the two latest TortoiseSVN releases.
>
> If you could provide access to the repository, or the URL of a public
> repo that shows the same problem then it would be a lot easier to
> debug. Without that we can only guess.
>
> Simon
>
> --
> : ___
> : oo // \\ "De Chelonian Mobile"
> : (_,\/ \_/ \ TortoiseSVN
> : \ \_/_\_/> The coolest Interface to (Sub)Version Control
> : /_/ \_\ http://tortoisesvn.net

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3001864

Simon Large

unread,
Aug 29, 2012, 6:58:15 PM8/29/12
to us...@tortoisesvn.tigris.org
On 29 August 2012 10:23, Eric DELAGE <Eric_...@hotmail.com> wrote:
> Hi
>
> Unfortunately, I can't give you any kind of access to the repository.
>
> This morning I discover something which may help. Using the same Apache/SSL/Subversion-1.7.6 setup and the same TortoiseSVN-1.7.7-8/SSL certificate on a Windows 7 Pro 64b and a Windows Vista Home 32b, I get different results. It works on Vista. It doesn't work on 7.

Joel Jirak has submitted a patch which has now been merged to the 1.7
branch and should hopefully fix the issue. I believe we are due
another release very shortly, but you could also check to see if there
is a stable branch build on the nightly build site and test that. You
need a build which is >= r23243.

http://nightlybuilds.tortoisesvn.net/1.7.x/

Simon

--
: ___
: oo // \\ "De Chelonian Mobile"
: (_,\/ \_/ \ TortoiseSVN
: \ \_/_\_/> The coolest Interface to (Sub)Version Control
: /_/ \_\ http://tortoisesvn.net

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3002026

Joel Jirak

unread,
Aug 31, 2012, 10:14:18 AM8/31/12
to us...@tortoisesvn.tigris.org
Eric Delage,

      Does 1.7.9 fix the " SSL error: cant get key" problem for you?

Joel

Eric DELAGE

unread,
Aug 31, 2012, 3:42:11 PM8/31/12
to us...@tortoisesvn.tigris.org
Hi Joel,

Thx for your help. I wanted to test it on all the platforms where we had the problem before I give a feedback.

It looks like it works now. We only have a problem on a VMware virtual machine hosting a Windows 7 Pro 64b where TortoiseSVN 1.7.9 seems to hang instead of showing the SSL error message (but AnkhSVN runs smoothly on the same virtual machine) but I haven't had time to look where the problem really comes from.

It's already a big big step in the right direction for us. So thx to the team for releasing a fix so quickly.

Eric

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3002550

balaka...@gmail.com

unread,
Nov 19, 2018, 10:50:27 AM11/19/18
to TortoiseSVN
Hi Team,
Greetings.
I am using Tortoise SVN 1.7.7. OS windows 10 64 bit.
When try to update i am getting the following error
Error: Unable to connect to a repository at URL 'svn+ssh://svn.meddiff.com/svn/support'
Error: To better debug SSH connection problems, remove the -q option from 'ssh' in the
Error: To better debug SSH connection problems, remove the -q option from 'ssh' in the
Error: [tunnels] section of your Subversion configuration file.
Error: Network connection closed unexpectedly


Please help me on this.

Thanks & regards,
Bala
(balaka...@gmail.com)

mr.pixnet

unread,
Nov 20, 2018, 10:32:56 AM11/20/18
to TortoiseSVN on behalf of Bala Kannan, tortoisesvn+unsubscribe

* Quote messages from < "tortoisesvn+APn2wQf55q1maYSIcjBVptrpj7airnf9SSUXJa3TZvQScXgsoWJT" <tortoisesvn+APn2wQf55q1maYSIcjBV...@googlegroups.com>> :
>--
>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 tortoisesvn...@googlegroups.com.
>To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/3e52d06e-4d03-45fd-adfa-f08b517b2eab%40googlegroups.com.
>For more options, visit https://groups.google.com/d/optout.
>
Reply all
Reply to author
Forward
0 new messages