gh-95341: Implement tls-exporter channel bindings and export key materials#95366
gh-95341: Implement tls-exporter channel bindings and export key materials#95366tiran wants to merge 6 commits into
Conversation
|
@tiran: Thanks for your PR! Can you add tls-exporter/9266 like tls-unique/5929 in files too? |
Sorry, something went wrong.
|
When it's ready. There is no need to rush this PR. The feature window for 3.12 is open for another 8 months. |
Sorry, something went wrong.
|
Hi @tiran, I see "v3.12.0a1" but it is without this PR :/ Can you look? Thanks in advance. |
Sorry, something went wrong.
Sorry, something went wrong.
|
@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. |
Sorry, something went wrong.
…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.
|
This PR is stale because it has been open for 30 days with no activity. |
Sorry, something went wrong.
|
Hi all; I'm just looking for a status update on this issue 🙏 |
Sorry, something went wrong.
edited by bedevere-bot
LoadingUh oh!
There was an error while loading. Please reload this page.
Copy link Copy MarkdownSorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.