We cannot remove it as that would be a break in backwards compatibility
maybe we can mark it deprecated
@golang/security @bradfitz

Hello, I have a WIP patch to add SCRAM-SHA-256 support. I tested it against Postfix with SMTP AUTH through Dovecot SASL.

The SCRAM algorithm requires pbkdf2 and according to RFC 5802 section 5.1 we have to apply the SASLprep profile [RFC4013] of the "stringprep" algorithm [RFC3454]. Since RFC 8265 obsoletes RFC 4013 I think we can use it instead. RFC 8265 is already implemented in golang.org/x/text/secure/precis.

So we need the following dependencies:

• golang.org/x/crypto
• golang.org/x/text

are they acceptable for net/smtp ?

@drakkan: Nice :)

It is possible to support SCRAM-SHA-1/SCRAM-SHA-1-PLUS, SCRAM-SHA-256/SCRAM-SHA-256-PLUS, SCRAM-SHA-512/SCRAM-SHA-512-PLUS, SCRAM-SHA3-512/SCRAM-SHA3-512-PLUS?
Not only 256.

For examples (more at the next link):

• Exim uses GNU SASL and support TLS Channel Binding
• Cyrus-SASL has more supports than Postfix/Dovecot

All details here:

• State of Play scram-sasl/info#1

@drakkan: Nice :)

It is possible to support SCRAM-SHA-1/SCRAM-SHA-1-PLUS, SCRAM-SHA-256/SCRAM-SHA-256-PLUS, SCRAM-SHA-512/SCRAM-SHA-512-PLUS, SCRAM-SHA3-512/SCRAM-SHA3-512-PLUS? Not only 256.

I haven't looked at channel binding for the PLUS variants yet. The other variants can be added easily but I'm a little worried about SHA-1, nowadays it's not considered secure anymore.

Before completing this work and submitting a CL, I would like to get feedback on the x/crypto and x/text dependencies from the net/smtp maintainers. I would like to avoid working on something that can't be merged

For examples (more at the next link):

• Exim uses GNU SASL and support TLS Channel Binding
• Cyrus-SASL has more supports than Postfix/Dovecot

All details here:

• State of Play scram-sasl/info#1

@drakkan: Thanks for your reply!

For example, SCRAM-SHA-1 and SCRAM-SHA-1-PLUS are used by default since a very long time by XMPP, you can see here:

• https://datatracker.ietf.org/doc/html/rfc6120 (March 2011)

To have a real compatibility with all products, it is needed to support SCRAM-SHA-*(-PLUS) included SHA-1.
Of course, it is better to use SCRAM-SHA-1 than CRAM-MD5/DIGEST-MD5/LOGIN/PLAIN.

Some products which support SCRAM-SHA-*(-PLUS) and SCRAM-SHA3-512(-PLUS):

• State of Play scram-sasl/info#1

About Channel Bindings -> RFC 9266: Channel Bindings for TLS 1.3:

• https://datatracker.ietf.org/doc/html/rfc9266

Little details, to know easily:

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