[SOLVED] mercurial and ssl problems

ebal · 2013-11-05 10:05:08

Upgraded to mercurial 2.8.1 and i am getting this error:

abort: error: _ssl.c:504: error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number

downgraded to 2.7.2-1 and everything is ok.

Tested on two different machines, checked openssl and every ssl library, checked by hand my ssl cert.

I pinpoint it to mercurial after cross checking the pacman.log

I am not 100% sure that this is a bug on building process or on upstream.

Did a quick search on forum & bugs but didnt find "exactly" the same, so i am posting this here.

Hope with this post to help others.

Last edited by ebal (2014-05-11 20:07:04)

jasonwryan · 2013-11-05 16:27:26

Works fine here. What else was in your upgrade?

ebal · 2013-11-06 05:52:33

a lot of staff, here is the list:

http://pastebin.com/f4yFsuuu

but after downgraded to mercurial 2.7.2 everything works fine again. Almost exactly the same packages on the second machine. I tried to downgrade python2-pyopenssl but got the same error with mercurial 2.8.1 so i upgraded python2-pyopenssl and downgrade mercurial.

The certificate i use is singed by cacert and the above error was on both machines on pull/push or even clone a new one.

jasonwryan · 2013-11-06 06:03:20

Run a stack trace to see if you can get any more information...

ebal · 2013-11-06 07:56:44

Here are my notes on the first PC (work PC)

http://ebalaskas.gr/img/mercurial_2.8.1_error.txt

be aware that this PC is behind a proxy and my hosts is created after winhelp2002.mvps.org/hosts.htm

haraldkl · 2013-11-06 14:26:45

I got exactly the same problem after upgrading mercurial today.

[2013-11-06 12:18] [PACMAN] upgraded mercurial (2.7.2-1 -> 2.8-1)

ebal · 2013-12-09 19:06:17

Do i need to open a bug report - or in the end is just me ?

haraldkl · 2013-12-11 16:04:10

It seems, that the problem disappeared now for me after upgrading to 2.8.1.

ebal · 2014-05-11 20:06:46

Today i have studied the problem more carefully and found the problem.

The problem is on SSL Handshake and specifically on the SSLProtocol that my server provide against the client openssl !

a simple "SSLProtocol All -SSLv2" on the (apache) server side fixed the issue.

So this wasnt in any case a mercurial or an archlinux problem.

Sorry

haraldkl · 2014-05-11 20:37:47

ebal wrote:

So this wasnt in any case a mercurial or an archlinux problem.

In fact it was a Mercurial problem and described here: http://bz.selenic.com/show_bug.cgi?id=4038. The problem was, that there was an Mercurial release which did not accept TLS connections anymore, but only SSLv3. However, this supposedly was solved by http://selenic.com/repo/hg/rev/47ff9d1abfa9

Arch Linux

#1 2013-11-05 10:05:08

[SOLVED] mercurial and ssl problems

#2 2013-11-05 16:27:26

Re: [SOLVED] mercurial and ssl problems

#3 2013-11-06 05:52:33

Re: [SOLVED] mercurial and ssl problems

#4 2013-11-06 06:03:20

Re: [SOLVED] mercurial and ssl problems

#5 2013-11-06 07:56:44

Re: [SOLVED] mercurial and ssl problems

#6 2013-11-06 14:26:45

Re: [SOLVED] mercurial and ssl problems

#7 2013-12-09 19:06:17

Re: [SOLVED] mercurial and ssl problems

#8 2013-12-11 16:04:10

Re: [SOLVED] mercurial and ssl problems

#9 2014-05-11 20:06:46

Re: [SOLVED] mercurial and ssl problems

#10 2014-05-11 20:37:47

Re: [SOLVED] mercurial and ssl problems

Board footer