Conversation
|
@kasparsd note that this relates to #423 (comment) wherein the next step after removing U2F is the determining the best path forward from here (happy to hear your input there). |
|
So this handles the code change, my only uncertainty at this point is whether we should do something to handle the data / ux. That being, if someone had U2F enabled, but no other providers, would its sudden absence disable 2fa on their account entirely, and is that a case in which we should force enable an alternative, such as emailed codes so there is still some second factor? |
Yeah, this is a really important point! Otherwise this looks good! |
|
@jeffpaul Do you have any thoughts on what the workflow should be if a user only has u2f enabled but no others? |
|
Hi, U2F will be removed in v.0.8 but it will be still possible to use physical keys with webauthn? #427 Also - when we can expect v.0.8 release? |
|
@georgestephanis if a user only has U2F enabled and the plugin is updated to whatever version this removal will be part of (e.g. 0.8.0), then we could possibly go with one of the following:
What are your thoughts on this? |
|
If we end up switching libraries in #427, then I think we could seamlessly migrate the existing U2F keys to the WebAuthn provider. |
b50326f to
db4ba40
Compare
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the Unlinked AccountsThe following contributors have not linked their GitHub and WordPress.org accounts: @dziudek. Contributors, please read how to link your accounts to ensure your work is properly credited in WordPress releases. If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
masteradhoc
left a comment
There was a problem hiding this comment.
Thanks for this PR @georgestephanis!
Can you check my small comments and commit them if its fine for you. the existing screenshots i already renamed so it will match my proposed commit.
Else PR looks good and can be merged. All noted U2F / Fido Texts were removed correctly and appropriate files removed.
Co-authored-by: Brian <brian@brianhaas.li>
Co-authored-by: Brian <brian@brianhaas.li>
Has been updated since and mitigated.
FIDO/U2F files will be removed entirely in PR WordPress#439, so changes to U2F.php and class-two-factor-fido-u2f-admin.php are unnecessary.
|
#815 broke this from merging cleanly. Lemme try to rebase. |
|
No more conflicts, I'd like to get this in before something else breaks it. @masteradhoc -- any objections to me just pulling the trigger once the tests clear? |
|
@georgestephanis Checks have successfully passed. all good from my side to get U2F out :) |
|
YEET |
As discussed with @jeffpaul with its deprecation we should remove the provider.