python
asyncio: Add PHA for TLS 1.3
| BPO | 34847 |
|---|---|
| Nosy | @fantix, @asvetlov, @1st1 |
| PRs |
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 2018-09-30.03:52:14.621>
labels = ['type-bug', '3.8', 'expert-asyncio']
title = 'asyncio: Add PHA for TLS 1.3'
updated_at = <Date 2018-09-30.03:54:16.138>
user = 'https://github.com/fantix'
bugs.python.org fields:
activity = <Date 2018-09-30.03:54:16.138>
actor = 'christian.heimes'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['asyncio']
creation = <Date 2018-09-30.03:52:14.621>
creator = 'fantix'
dependencies = []
files = []
hgrepos = []
issue_num = 34847
keywords = ['patch']
message_count = 1.0
messages = ['326700']
nosy_count = 3.0
nosy_names = ['fantix', 'asvetlov', 'yselivanov']
pr_nums = ['9460']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue34847'
versions = ['Python 3.8']
This was raised in GH-9460 where the same post handshake authentication (PHA) was added to the ssl module. It should be added to asyncio too. This issue is to discuss the design of PHA API in asyncio, and implement it in Python 3.8.
One approach is to add _SSLProtocolTransport.verify_client_post_handshake(), but an additional new transport mixin type to asyncio/transports.py would be needed (Yury).
Yury also proposed another option to use get_extra_info() API to get something like an "SSLExtra" object with additional APIs.
There have been no user requests for this feature and we are unlikely to expand the tls API hence closing.
In case this is still being read I was hoping for this functionality to support creating a WSMan service for Windows Event Forwarding. The WSMan service uses the post handshake auth feature for certificate authentication.
All good I assumed as much, just wanted to put it out there some use cases of such a feature. I'm looking into alternatives but alas I think I need to manually wrap my data with wrap_bio as the sync variant only seems to work when you send actual data with no way of just doing the new handshake only.