Skip to content
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

Opt-in for MFA requirement #1758

Closed
wants to merge 1 commit into from

Conversation

tagliala
Copy link

Make the gem more secure by requiring that all privileged operations by any of the owners require OTP.

Ref: https://guides.rubygems.org/mfa-requirement-opt-in/

Make the gem more secure by requiring that all privileged operations by
any of the owners require OTP.

Ref: https://guides.rubygems.org/mfa-requirement-opt-in/
@olleolleolle
Copy link
Contributor

The most important bit for maintainers will then be to check that the API key used has been allowed to stand in for MFA.

https://guides.rubygems.org/api-key-scopes/

ENABLE MFA ON SPECIFIC API KEYS

If your account has MFA enabled on the UI only or UI and gem signin authentication level, you have the option to enable MFA on a specific API key. This will require an OTP code for gem push, yank, owner --add/--remove commands.

You can toggle this option when creating or editing an API key on the UI. New API key with MFA enabled

@luke-hill
Copy link
Contributor

Because we've not updated rubocop here for a while. See https://github.com/cucumber/cucumber-rails/blob/main/.rubocop.yml#L18 for a brief comment ditty on why this isn't the case. This won't be something we have capacity to change soon

@luke-hill luke-hill closed this Aug 8, 2024
@tagliala
Copy link
Author

tagliala commented Aug 8, 2024

Ok thanks, got it, the current release process doesn't play well with MFA

@tagliala tagliala deleted the security/opt-in-for-mfa branch August 8, 2024 11:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants