We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently, rubygems.org only supports TOTP as a second factor. This is not phishing-resistant.
Security keys are support by Google, Microsoft, Facebook, Twitter, Dropbox, GitHub, AWS, WordPress.com and others.
The text was updated successfully, but these errors were encountered:
Thanks for rising this. Can you discuss this topic on #2792?
Sorry, something went wrong.
Looks like #2108 has work done, but is stale.
We also tried this with #2865. This one is not as stale. Someone needs to update it and resubmit.
I've reopened #2865 and am working on getting that up to date so we can push forward with WebAuth support
No branches or pull requests
Is your feature request related to a problem?
Currently, rubygems.org only supports TOTP as a second factor. This is not phishing-resistant.
Describe the solution you'd like
Additional context
Security keys are support by Google, Microsoft, Facebook, Twitter, Dropbox, GitHub, AWS, WordPress.com and others.
The text was updated successfully, but these errors were encountered: