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
This issue is to track the CFRG PAKE selection process going on in the IETF. When that process completes, if they pick a PAKE other than SPAKE2, we should consider swapping out SPAKE2 if there are no implementations shipped yet.
They aren't tracking progress in GitHub, instead conversations are happening on the cfrg@ietf.org mailing list. I will set myself up to lurk there to monitor progress.
The text was updated successfully, but these errors were encountered:
The panel of experts made the following recommendations:
We recommend the following two protocols to be selected as «recommended by
the CFRG for usage in IETF protocols»: one balanced PAKE - CPace, and one
augmented PAKE - OPAQUE.
The next steps are to evaluate the assumptions and suitability of these two algorithms for our use case, and possibly follow up with the IETF draft author(s) with any questions or feedback.
This issue is to track the CFRG PAKE selection process going on in the IETF. When that process completes, if they pick a PAKE other than SPAKE2, we should consider swapping out SPAKE2 if there are no implementations shipped yet.
https://github.com/cfrg/pake-selection
They aren't tracking progress in GitHub, instead conversations are happening on the cfrg@ietf.org mailing list. I will set myself up to lurk there to monitor progress.
The text was updated successfully, but these errors were encountered: