Mercurial > hg
comparison mercurial/sslutil.py @ 29042:693b856a4d45 stable
sslutil: restore old behavior not requiring a hostname argument (issue5210)
This effectively backs out changeset 1fde84d42f9c.
The http library behind ui.http2=true isn't specifying the hostname.
It is the day before the expected 3.8 release and we don't want to ship
a regression.
I'll try to restore this requirement in the 3.9 release cycle as part
of planned improvements to Mercurial's SSL/TLS interactions.
author | Gregory Szorc <gregory.szorc@gmail.com> |
---|---|
date | Sat, 30 Apr 2016 09:26:47 -0700 |
parents | 3819c349b194 |
children | 548e9c8c2841 26a5d605b868 |
comparison
equal
deleted
inserted
replaced
29041:b962ae0a0a05 | 29042:693b856a4d45 |
---|---|
118 | 118 |
119 * serverhostname - The expected hostname of the remote server. If the | 119 * serverhostname - The expected hostname of the remote server. If the |
120 server (and client) support SNI, this tells the server which certificate | 120 server (and client) support SNI, this tells the server which certificate |
121 to use. | 121 to use. |
122 """ | 122 """ |
123 if not serverhostname: | |
124 raise error.Abort('serverhostname argument required') | |
125 | |
126 # Despite its name, PROTOCOL_SSLv23 selects the highest protocol | 123 # Despite its name, PROTOCOL_SSLv23 selects the highest protocol |
127 # that both ends support, including TLS protocols. On legacy stacks, | 124 # that both ends support, including TLS protocols. On legacy stacks, |
128 # the highest it likely goes in TLS 1.0. On modern stacks, it can | 125 # the highest it likely goes in TLS 1.0. On modern stacks, it can |
129 # support TLS 1.2. | 126 # support TLS 1.2. |
130 # | 127 # |