Rémi Cardona added the comment:
Anything I can do to get the ball rolling? Let me know who to get in touch
with and *how*, and I will. Thanks
--
___
Python tracker
<https://bugs.python.org/issue34
Rémi Cardona added the comment:
So, IOW, the ssl module needs a good shakeup wrt TLS 1.3 sessions before any
asyncio work can be merged. Am I getting this right?
In which case, a whole other issue/PR is needed and possibly better folks than
me. I try to stay clear of low-level crypto APIs
Rémi Cardona added the comment:
Hi Christian,
Could you tell me more about this new openssl API? Right now my patch works
with whatever the ssl module provides. Are you suggesting the ssl module is in
some way incomplete? Would supporting TLS 1.3 sessions be incompatible with the
current
Rémi Cardona added the comment:
Hi Andrew,
How should I proceed? What's the best avenue to get in touch with Yuri?
Thanks
--
___
Python tracker
<https://bugs.python.org/issue34
Change by Rémi Cardona :
--
keywords: +patch
pull_requests: +9214
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue34971>
___
___
Py
New submission from Rémi Cardona :
cpython has had TLS session support since 3.6, using the SSLContext.wrap_*
methods. Unfortunately, this support is not available when using asyncio's
create_connection.
While I've managed to monkeypatch asyncio.sslproto._SSLPipe from my own code
(it's
Rémi Cardona added the comment:
Got hit by this too, many times as I'm working with 3G devices (slow write
speeds).
As for "drain()", I'd say it should work like a fence/barrier: to let you know
that the bytes in the buffer up to when the call was issued have been
successful
Changes by Rémi Cardona <remi2...@free.fr>:
--
nosy: +RemiCardona
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue29309>
___
__
Changes by Rémi Cardona <remi2...@free.fr>:
--
nosy: +RemiCardona
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue26081>
___
__
