Skip to content
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

Support the tls-exporter channel binding #9

Open
tlocke opened this issue Jan 10, 2022 · 4 comments
Open

Support the tls-exporter channel binding #9

tlocke opened this issue Jan 10, 2022 · 4 comments

Comments

@tlocke
Copy link
Owner

tlocke commented Jan 10, 2022

The tls-exporter channel binding is described in https://datatracker.ietf.org/doc/html/draft-ietf-kitten-tls-channel-bindings-for-tls13. This probably can't be implemented until Python allows access to Exported Keying Material, see https://bugs.python.org/issue37952

@Neustradamus
Copy link

Neustradamus commented Jul 25, 2022

It is official, it is here: RFC 9266: Channel Bindings for TLS 1.3:

@tlocke
Copy link
Owner Author

tlocke commented Jul 31, 2022

As far as I can see, in order to implement the tls-exporter channel binding we'd need to be able to get the EKM, which we can't do at the moment:

python/cpython#82133

@tlocke
Copy link
Owner Author

tlocke commented Nov 19, 2023

Thanks @Neustradamus, I've had a look at the links and I assume these are just updates on the situation, rather than anything we need to do with Scramp?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants