[issue2596] mercurial fails when connecting to a server with a self-signed SSL certificate

[Eric Haszlakiewicz]

New submission from Eric Haszlakiewicz <ehaszla at transunion.com>:

The most recent version of Mercurial is stricter about connecting to servers
with self-signed SSL certificates.  For instance, attempting to pull results in:
hg pull
abort: error: _ssl.c:480: error:14090086:SSL
routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed

This is a huge usability regression, and I think the change should be reversed.

IMO, the correct way to handle this is to prompt the user for a desired
course of action.  There should be three choices:
  do not connect (abort the operation)
  temporarily allow the connection for this command
  save the particular server name and certificate permanently.

----------
messages: 14927
nosy: erh
priority: urgent
status: unread
title: mercurial fails when connecting to a server with a self-signed SSL certificate

____________________________________________________
Mercurial issue tracker <bugs at mercurial.selenic.com>
<http://mercurial.selenic.com/bts/issue2596>
____________________________________________________