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
{{ message }}
This repository has been archived by the owner on Oct 12, 2022. It is now read-only.
When a list of user ids (usernames/emails)/passwords from a compromised site is obtained, the system should facilitate
Testing if a user used the same password on that other site in real time if the password is known.
Testing the next time the users' correct password is entered if we only have a hash of the password (but know the hash function).
Adding an attribute to the account so that it can be searched easily and so password-reset can be enforced.
Revoking any cookies created after the suspected date of compromise or otherwise provide less benefit to having such a cookie.
Optionally prevent all logins from clients that do not have cookies that predate the compromise.
Track compromised passwords as a new type to use when penalizing blocking attacks. The use of a compromised password from an iP the user has logged in before may be an indicator that an IP is trying to login with these passwords.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When a list of user ids (usernames/emails)/passwords from a compromised site is obtained, the system should facilitate
The text was updated successfully, but these errors were encountered: