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

Add support for channel binding #4

Open
xdg opened this issue Nov 14, 2020 · 3 comments
Open

Add support for channel binding #4

xdg opened this issue Nov 14, 2020 · 3 comments

Comments

@xdg
Copy link
Contributor

xdg commented Nov 14, 2020

See RFC-5802 Sec 6.

@Neustradamus
Copy link

@xdg: Thanks!

@Neustradamus
Copy link

It is official for TLS 1.3 Binding!

Details:

  • tls-unique for TLS =< 1.2
  • tls-exporter for TLS = 1.3

@ehuelsmann
Copy link

@xdg Thank you for creating this module! It allowed me to implement a wrapper module to plug into Authen::SASL and have a working prototype within hours! I've published a more complete version on CPAN under the name Authen::SASL::SCRAM. With this new dist, I was able to add SCRAM-SHA-512 to a Perl program called sendxmpp without changing a single line of code to the original!

I'm now researching the possibilities to add support channel binding to the Authen::SASL::SCRAM dist, both for completeness as well as because the server that the sendxmpp application is talking to, supports it. I've shortly looked at whether it's possible for me to support channel binding without bothering you, but that's unfortunately not the case due to the impact on the messages being exchanged being tracked by Authen::SCRAM.

So: could you please consider implementing channel binding, so I can add support for it to the Authen::SASL::SCRAM dist?

If you provide me with directions on how you want it added to your module, I'm willing to do the legwork and provide you with a PR as well.

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

3 participants