-
-
Notifications
You must be signed in to change notification settings - Fork 30.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gh-95341: Implement tls-exporter channel bindings and export key materials #95366
base: main
Are you sure you want to change the base?
Conversation
tiran
commented
Jul 28, 2022
•
edited by bedevere-bot
Loading
edited by bedevere-bot
- Issue: ssl module incorrectly supports tls-unique channel binding for TLS 1.3 #95341
@tiran: Thanks for your PR! Can you add tls-exporter/9266 like tls-unique/5929 in files too? |
@tiran: Have you an idea when it will be merged? Thanks for your work! |
When it's ready. There is no need to rush this PR. The feature window for 3.12 is open for another 8 months. |
@tiran: Thanks for your answer! No problem ^^ |
Hi @tiran, I see "v3.12.0a1" but it is without this PR :/ Can you look? Thanks in advance. |
any news about this @tiran ? |
@tiran: I think that you have seen the jabber.ru MITM:
Can you add "tls-server-end-point" from RFC5929 too? It is needed for all SCRAM-SHA-*-PLUS (several RFCs) and specified in:
Thanks in advance. |
…o as to get channel binding data for the current SSL session (only the "tls-unique" channel binding is implemented). This allows the implementation of certain authentication mechanisms such as SCRAM-SHA-1-PLUS. Patch by Jacek Konieczny.