[issue21025] if check_hostname is true, context can't be used for server purposes
New submission from Antoine Pitrou: On a SSLContext with check_hostname = True, calling wrap_socket(..., server_side=True) will complain that no server hostname has been passed. This should only be done for client sockets. -- components: Library (Lib) messages: 214462 nosy: christian.heimes, giampaolo.rodola, janssen, pitrou priority: normal severity: normal status: open title: if check_hostname is true, context can't be used for server purposes type: behavior versions: Python 3.4, Python 3.5 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21025 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21025] if check_hostname is true, context can't be used for server purposes
Changes by Antoine Pitrou pit...@free.fr: -- nosy: +dstufft ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21025 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue21025] if check_hostname is true, context can't be used for server purposes
Antoine Pitrou added the comment: (of course, it may be better to have separate contexts for client and server use, but it can also be convenient to use a single context - especially when doing tests :-)) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21025 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
