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
Upstream in the two-factor plugin, they were renamed to Recovery Codes (albeit, by me) in WordPress/two-factor#521
That upstream rename has flowed through to the login screen:
These are not at all a "backup" (a copy of..) nor are they intended on active use by the holder, rather, it's intended on being an emergency-access or "recover your account access" type scenario. At least in my mind. It may be better to call them Emergency Account Access token even.
We should just standardise on one or the other, whatever that may be.
The text was updated successfully, but these errors were encountered:
WordPress.com calls them Backup codes, but also has a separate 'Recovery' process.
GitHub
GitHub calls it a recovery code, and also has a 2FA recovery process
Google
Calls them Backup Codes
Facebook
Calls them Recovery Codes
Slack
Calls them Backup Codes
It appears that it doesn't really matter what it's called, as long as it's documented somewhere. Most of the services that use Backup seem to also have a Recovery process.
bazza
pushed a commit
to WordPress/wordpress.org
that referenced
this issue
Aug 20, 2024
As raised in WordPress/wordpress.org#358 (comment) I've been using 'Recovery code' in text, but wporg-two-factor uses
Backup Codes
.Upstream in the two-factor plugin, they were renamed to Recovery Codes (albeit, by me) in WordPress/two-factor#521
That upstream rename has flowed through to the login screen:
These are not at all a "backup" (a copy of..) nor are they intended on active use by the holder, rather, it's intended on being an emergency-access or "recover your account access" type scenario. At least in my mind. It may be better to call them
Emergency Account Access token
even.We should just standardise on one or the other, whatever that may be.
The text was updated successfully, but these errors were encountered: