Skip to content

Add support for SCRAM-SHA-*-PLUS channel binding in PHP streams (e.g., tls-unique, tls-exporter) #16766

Open

Description

@fabiang

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:

  • 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.

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:

  • return data from OpenSSL's SSL_get_peer_finished when channel binding is set to "tls-unique" and TLS 1.2 is used,
  • use OpenSSL's SSL_export_keying_material when channel binding is set to "tls-exporter" and TLS <= 1.3 is used,
  • trigger a warning when "tls-unique" is used with TLS 1.3,
  • and trigger an error if the stream or context is not a TLS connection.

(Note: "tls-exporter" should also be supported on TLS 1.2 connections.)

stream_crypto_channel_binding(resource $stream_or_context, string $channel_binding_type): string;

Making this function compatible with both streams and contexts should cover all use cases.

Thank you.

Activity

  1. Neustradamus commented on Nov 13, 2024

    @Neustradamus

    @fabiang: Thanks for your ticket, a lot of PHP projects wait the solution to add -PLUS variants.

  2. Neustradamus commented on Jan 15, 2025

    @Neustradamus

    Dear @php team,

    Have you progressed on this ticket?

  3. bukka commented on Jan 19, 2025

    @bukka
    Member

    There are still bunch of open bug for tls streams so I won't be probably able to get to it anytime soon but if someone else creates a PR containing tests, I should be able to review it.

  4. Neustradamus commented on Jan 19, 2025

    @Neustradamus

    @bukka: Thanks for your answer!

    It is always possible to work on it before to solve all other bugs?

    This feature is very important and permit to have more security...

  5. Neustradamus commented on Feb 3, 2025

    @Neustradamus

    @bukka: For your information, the recent Dovecot 2.4.0 has SCRAM-SHA-1-PLUS/SCRAM-SHA-256-PLUS supports in more SCRAM-SHA-1/SCRAM-SHA-256. It arrives after Exim, indimail-mta, msmtp, mpop, ...

    About PHP, SCRAM has been added in, people wait for -PLUS variants:

    • PEAR Auth_SASL/Auth_SASL2/Net_SMTP (used by a lot of projects like Roundcube etc.)
    • SnappyMail
    • SquirelMail
    • Horde

    Linked to:

  6. Neustradamus commented on Mar 3, 2025

    @Neustradamus

    Dear @php team, @bukka, @fjanisze,

    For information: @fabiang has released the 2.0.0 release build of PHP SASL2 Authentification Library:

    The only missing point is Channel Binding :/

    Hope that you will solved this problem.

    Thanks in advance.

    cc: @jfha73

  7. bukka commented on Mar 3, 2025

    @bukka
    Member

    @Neustradamus Bugs and especially security issues are the highest priority so I cannot prioritise this over them. We have got other important features requested for OpenSSL as well (there are many things missing). I understand that this is a priority for you but you will either need to implement it yourself and create a PR or hire someone to do that if you can't do that. Just pinging people will not change their priorities.

  8. Neustradamus commented on Oct 24, 2025

    @Neustradamus

    Little details, to know easily:

    • tls-unique for TLS =< 1.2 (RFC5929)
    • tls-server-end-point for TLS =< 1.2 + 1.3 (RFC5929)
    • tls-exporter for TLS = 1.3 (RFC9266)
  9. Neustradamus commented on Dec 4, 2025

    @Neustradamus

    Dear PHP Security team, @bukka,

    Have you progressed about this important PHP security point?

    This is missing since a long time and @fabiang has done this ticket more one year ago.

    Can you see to have this security support into all PHP >= 8.2?

    Thanks in advance.


    More informations:

    IANA: Simple Authentication and Security Layer (SASL) Mechanisms: https://www.iana.org/assignments/sasl-mechanisms/sasl-mechanisms.xhtml

    Channel Binding RFCs:

    Linked RFCs:

    Current IETF Internet-Drafts:


  10. Neustradamus commented on Sep 30, 2026

    @Neustradamus

    Dear PHP Security team, @bukka,

    Have you progressed about this important PHP security point?

    This is missing since a long time and @fabiang has done this ticket two year ago.

    Can you see to have this security support into all PHP version?

    Thanks in advance.

  11. Sjord commented on Oct 1, 2026

    @Sjord
    Contributor

    @fabiang, @Neustradamus, could you take a look at #24035? Would that solve your use case?

    Can you see to have this security support into all PHP version?

    This is unlikely to happen; it will probably be in PHP 8.7 and up.

  12. Neustradamus commented on Oct 2, 2026

    @Neustradamus

    @Sjord: Thanks a lot for your work about Channel Binding!

    I have requested tests to PHP project devs...

    It will be not possible to backport to previous PHP versions too?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions