Has anyone been able to integrate with BitBucket (Phase 5 Step 5.6) since SSLv3 has been disabled to avoid the POODLE vulnerability?

Craig Drummond

In September 2014 the POODLE vulnerability was disclosed.  Since then Atlassian has correctly decided to disable SSLv3 on their cloud servers including BitBucket.  However this is a problem for making it through the Dragon Slayer steps on a Linux OS because Mercurial hg version 2.7 will fail to connect.  

For windows users it seems that an updated version of TortoiseHG is now available that resolves this problem.

Anyone know when an update to hg 2.7 for Linux (openSuSE 13.1) will be released?  Is there an alternative to hg?

Thanks,

Craig

lpater

Hi Craig,

there is an issue with Mercurial 2.7 TLS support (http://bz.selenic.com/show_bug.cgi?id=4038), which might cause problems when connecting to servers with SSLv3 disabled. These seem to have been fixed in Mercurial 2.7.2 and 2.8 (released October/November 2013).

There seem to be mercurial packagages with new versions at http://download.opensuse.org/repositories/devel:/tools:/scm/, for example: http://download.opensuse.org/repositories/devel:/tools:/scm/openSUSE_13.1/x86_64/mercurial-3.1.2-132.2.x86_64.rpm