Require MFA for gem pushes #10239
Merged
Require MFA for gem pushes #10239
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Yes and yes! Thanks! |
This was referenced Nov 12, 2021
willnet
added a commit
to willnet/delayed_job_active_record
that referenced
this pull request
Nov 15, 2021
willnet
added a commit
to willnet/delayed_job_active_record
that referenced
this pull request
Nov 15, 2021
willnet
added a commit
to willnet/delayed_job_active_record
that referenced
this pull request
Nov 22, 2021
willnet
added a commit
to willnet/delayed_job_active_record
that referenced
this pull request
Nov 22, 2021
willnet
added a commit
to willnet/delayed_job_active_record
that referenced
this pull request
Nov 22, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Ruby gems now allows MFA to be required for pushes: https://guides.rubygems.org/mfa-requirement-opt-in/
This allows users to have confidence that the actual authors were responsible for updates (obviously that doesn't mean that it can't be a malicious update, but at least it's not from someone who got access to a pusher's account).
I don't have push access but I hope all of us who do have MFA set up anyways (and if anyone doesn't it's easy to set up).
If this is acceptable, I'd like to create a cop to check for this as well.