if check_hostname is true, context can't be used for server purposes

[pitrou]

BPO	21025
Nosy	@pitrou, @giampaolo, @tiran, @dstufft

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = None
created_at = <Date 2014-03-22.11:35:11.719>
labels = ['type-bug', 'library']
title = "if check_hostname is true, context can't be used for server purposes"
updated_at = <Date 2014-03-22.17:25:12.431>
user = 'https://github.com/pitrou'

bugs.python.org fields:

activity = <Date 2014-03-22.17:25:12.431>
actor = 'pitrou'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2014-03-22.11:35:11.719>
creator = 'pitrou'
dependencies = []
files = []
hgrepos = []
issue_num = 21025
keywords = []
message_count = 2.0
messages = ['214462', '214492']
nosy_count = 5.0
nosy_names = ['janssen', 'pitrou', 'giampaolo.rodola', 'christian.heimes', 'dstufft']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue21025'
versions = ['Python 3.4', 'Python 3.5']

[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.

[pitrou]

(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 :-))

[photon-e]

@ezio-melotti looks like this issue needs to be closed