[WIP] MSC3726: Safer Password-based Authentication with BS-SPEKE #3726
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Charles Wright <cvwright@futo.org>
turt2live
changed the title
turt2live
added
client-server
jvoisin
reviewed
Feb 18, 2022
| However those patents expired in 2011 and 2017, respectively, and | ||
| as a result, SPEKE-derived protocols like BS-SPEKE can now be used freely. | ||
|
|
||
| BS-SPEKE comes highly recommended by experts in applied cryptography, |
There was a problem hiding this comment.
Can you please provide citations for this claim?
There was a problem hiding this comment.
I can't say anything about it being recommended, but as far as the patents are concerned,
EKE: https://en.wikipedia.org/wiki/Encrypted_key_exchange => https://patents.google.com/patent/US5241599 & https://patents.google.com/patent/US5440635
SPEKE: https://en.wikipedia.org/wiki/SPEKE#History => https://patents.google.com/patent/US6226383
They seem to have expired.
There was a problem hiding this comment.
@jvoisin The recommendation is mostly Thomas Ptacek yelling at me on Hacker News to use BS-SPEKE instead of SRP. Not exactly a peer-reviewed publication, but still his word means a lot in this space.
Signed-off-by: Charles Wright <cvwright@futo.org>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Rendered
This proposal serves as a sort of update to MSC3262. The main difference is a change from one password-authenticated key exchange (PAKE) protocol, SRP6a, to a more modern PAKE protocol, BS-SPEKE.
This also deprecates MSC3265, which proposed doing a bunch of client-side hashing to prevent the server from learning the user's "real" password.