Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding note on password change #436

Merged
merged 1 commit into from
Dec 7, 2023
Merged

Adding note on password change #436

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions draft-irtf-cfrg-opaque.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1828,6 +1828,11 @@ applications can use to control OPAQUE:
implement this mitigation SHOULD use the same configuration information (such as
the oprf_seed) for all clients; see {{preventing-client-enumeration}}. In settings
where this attack is not a concern, servers may choose to not support this functionality.
- Handling password changes: In the event of a password change, the client and
server can run the offline registration phase using the new password as a
fresh instance (ensuring to resample all random values). The resulting
registration record can then replace the previous record corresponding to
the client's old password registration.

# Implementation Considerations {#implementation-considerations}

Expand Down
Loading