You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm the maintainer of the fabiang/sasl library, which implements various SASL mechanisms. Since many SASL mechanisms have been deprecated over the years due to security issues, I am interested in improving the security of the SCRAM-SHA-* SASL mechanisms.
The SCRAM-SHA-*-PLUS mechanisms offer better security through channel binding. The recommended channel binding types are:
tls-unique for TLS <= 1.2
tls-server-end-point
tls-exporter for TLS >= 1.3
Currently, PHP lacks support for channel binding, as no API is exposed to access data from the underlying secure socket. Additionally, more and more server software is adding support for channel binding.
Description
Hello,
I'm the maintainer of the fabiang/sasl library, which implements various SASL mechanisms. Since many SASL mechanisms have been deprecated over the years due to security issues, I am interested in improving the security of the SCRAM-SHA-* SASL mechanisms.
The SCRAM-SHA-*-PLUS mechanisms offer better security through channel binding. The recommended channel binding types are:
Currently, PHP lacks support for channel binding, as no API is exposed to access data from the underlying secure socket. Additionally, more and more server software is adding support for channel binding.
For example, Python:
To enable this in PHP, a simple API to retrieve channel binding data from a stream context would be beneficial.
A potential function could:
SSL_get_peer_finished
when channel binding is set to "tls-unique" and TLS 1.2 is used,SSL_export_keying_material
when channel binding is set to "tls-exporter" and TLS <= 1.3 is used,(Note: "tls-exporter" should also be supported on TLS 1.2 connections.)
Making this function compatible with both streams and contexts should cover all use cases.
Thank you.
The text was updated successfully, but these errors were encountered: