-
Notifications
You must be signed in to change notification settings - Fork 1k
feat: unverify expired domains #18055
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.
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
base: main
Are you sure you want to change the base?
feat: unverify expired domains #18055
Conversation
With domain status checking now in place, add a task to unverify any email address that is in one of the statuses considered "expired". Add an Observation on the User, as well updates the unverify reason. Signed-off-by: Mike Fiedler <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure I see the point in doing this as-is: an attacker can still just register the expired domain, issue a password reset request to the un-verified email, and gain access to the account.
I think instead we probably need to either prevents sending password resets to unverified emails, add a different verification state that prevents sending reset requests to these emails (an 'expired' status?) or just remove the email from the account entirely.
unverify + freeze? |
That would work but would probably be the most support-intensive option. |
With domain status checking now in place, add a task to unverify any email address that is in one of the statuses considered "expired".
Add an Observation on the User, as well updates the unverify reason.