Closed Neustradamus closed 2 years ago
Let's keep the discussion in #95341
All links about it:
cc: @davidben, @wingel, @eighthave, @jchampio, @gst, @lowinger42, @ezio-melotti, @AlexWaygood, @njsmith, @zooba, @tlocke, @agronholm, @oberstet.
Dear @Python team,
I have done a new ticket for the "tls-exporter", because this ticket has been closed without a security solution.
The initial ticket has been created in 2022, we are in 2024, no security changes have been done.
I have done another ticket for the missing "tls-server-end-point" part too:
Several projects are blocked because it is not in CPython...
It is possible to have a PR, a commit with the security solution for "tls-exporter", and another one for "tls-server-end-point"?
Thanks in advance.
Please use the issue you were directed to use.
Can you add the support of RFC 9266: Channel Bindings for TLS 1.3?
Little details, to know easily:
I think that you have seen the jabber.ru MITM:
It is needed for all SCRAM-SHA-*-PLUS (several RFCs) and specified in:
A best SCRAM SASL and Channel Binding explanation:
An announcement has been done by Slixmpp team here about the security problem:
Thanks in advance.
Linked to: