Mercurial > hg-stable
changeset 29557:53de8255ec4e
sslutil: update comment about create_default_context()
While ssl.create_default_context() creates a SSLContext with
reasonable default options, we can't use it because it conflicts with
our CA loading controls. So replace the comment with reality.
(FWIW the comment was written before the existing CA loading code
was in place.)
| author | Gregory Szorc <gregory.szorc@gmail.com> |
|---|---|
| date | Thu, 14 Jul 2016 19:56:39 -0700 |
| parents | 1b8b6adb2365 |
| children | a935cd7d51a6 |
| files | mercurial/sslutil.py |
| diffstat | 1 files changed, 7 insertions(+), 1 deletions(-) [+] |
line wrap: on
line diff
--- a/mercurial/sslutil.py Wed Jul 13 20:41:07 2016 -0700 +++ b/mercurial/sslutil.py Thu Jul 14 19:56:39 2016 -0700 @@ -264,7 +264,13 @@ settings = _hostsettings(ui, serverhostname) - # TODO use ssl.create_default_context() on modernssl. + # We can't use ssl.create_default_context() because it calls + # load_default_certs() unless CA arguments are passed to it. We want to + # have explicit control over CA loading because implicitly loading + # CAs may undermine the user's intent. For example, a user may define a CA + # bundle with a specific CA cert removed. If the system/default CA bundle + # is loaded and contains that removed CA, you've just undone the user's + # choice. sslcontext = SSLContext(settings['protocol']) # This is a no-op unless using modern ssl.