>>> 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:
> > On Tue, Aug 28, 2012 at 12:08 PM, Eric DELAGE <eric_delage at hotmail dot 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=3001676
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2012-08-28 18:43:34 CEST