On 24.01.19 15:38, Evgeny wrote: > Hi there. > > Can someone please clarify how to maintain ineroperablity of > SCRAM-SHA1 vs SCRAM-SHA256 vs SCRAM-SHA-WHATEVER, e.g. > when some clients support SCRAM-SHA1 only, but the password > was created in SCRAM-SHA256 format.
Then you can't authenticate unless the server also stores the authentication data for SCRAM-SHA1. I guess that is your point. What is wrong with the server storing the required data to authenticate clients with eg. SCRAM-SHA1 or SCRAM-SHA256 (besides the implementation overhead argument)? Maybe I am missing something? >> After publication of [RFC5802], it was discovered that Transport >> Layer Security (TLS) [RFC5246] does not have the expected properties >> for the "tls-unique" channel binding to be secure [RFC7627] > > Does that mean that "-PLUS" doesn't provide additional security > and is now useless? No, only when tls-unique is used and if RFC 7627 is *not* used. - Florian
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
