Message 379908 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	Dima.Tisnek
Recipients	Dima.Tisnek, christian.heimes
Date	2020-10-30.02:24:04
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1604024645.33.0.358615043309.issue42200@roundup.psfhosted.org>
In-reply-to

Content
(apologies if this was raised before, I couldn't find it in bugs, mailing lists or discourse). (also apologies if I misunderstood something about the protocol) Up to an including TLS 1.2, a single close notify terminates both upstream and downstream; Starting with TLS 1.3 there are separate close notify alerts for upstream and downstream. This means that it's possible to have a TLS connection in half-closed state, e.g. to send "GET / HTTP xx; close notify" and then wait for the server response. Today, that's not possible, at least in asyncio, as evidenced by https://bugs.python.org/issue39951 (I did not check synchronous wrapped sockets)

(apologies if this was raised before, I couldn't find it in bugs, mailing lists or discourse).
(also apologies if I misunderstood something about the protocol)

Up to an including TLS 1.2, a single close notify terminates both upstream and downstream; Starting with TLS 1.3 there are separate close notify alerts for upstream and downstream.

This means that it's possible to have a TLS connection in half-closed state, e.g. to send "GET / HTTP xx; close notify" and then wait for the server response.

Today, that's not possible, at least in asyncio, as evidenced by https://bugs.python.org/issue39951 
(I did not check synchronous wrapped sockets)

History
Date	User	Action	Args
2020-10-30 02:24:05	Dima.Tisnek	set	recipients: + Dima.Tisnek, christian.heimes
2020-10-30 02:24:05	Dima.Tisnek	set	messageid: <1604024645.33.0.358615043309.issue42200@roundup.psfhosted.org>
2020-10-30 02:24:05	Dima.Tisnek	link	issue42200 messages
2020-10-30 02:24:04	Dima.Tisnek	create