-
Notifications
You must be signed in to change notification settings - Fork 126
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
RFC 9266: Channel Bindings for TLS 1.3 support #3140
Comments
@Neustradamus hi, is there a server where I could test this feature? |
@georgehazan: Hi Georges, Thanks for your answer! About XMPP Servers: Djabberd has a ticket: ejabberd has a ticket: Jackal has a PR: Metronome IM has a ticket: Mongoose IM has a ticket: Prosody IM has added the support few days ago: Tigase XMPP Server has a ticket: About XMPP Clients: CoyIM has a PR: About XMPP Libraries: Mellim SASL has a commit: |
Aha, Prosody is ok, I'll upgrade my server |
@Neustradamus I've added some code and tested that it really reports some data. Unfortunately, I hadn't verified it with the real server, because I still don't have the version of Prosody that supports it. |
@georgehazan: Thanks for your changes! You can not try with Prosody trunk? |
@georgehazan: Have you looked for "tls-server-end-point"? |
@georgehazan: Have you looked for "tls-server-end-point" in more "tls-unique" and "tls-exporter"? It is supported by:
|
The problem is where to get Prosody Trunk... I have Ubuntu on my desktop, and it comes with the previous version, those SASL fixes were introduced only 8 weeks ago |
@georgehazan: You can try the ejabberd master code with deps too... For Prosody IM, it is here: |
@georgehazan: Have you tested? |
Can you add the support of RFC 9266: Channel Bindings for TLS 1.3?
Little details, to know easily:
Thanks in advance.
Linked to:
The text was updated successfully, but these errors were encountered: