Restrict movement of packages to trusted sources only#327
Merged
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Closes #65
Introduces the notion of trusted sources (for packages that is; the later implemented libraries have this baked in). Only movements to trusted sources are allowed.
Additionally, fatally failing packages (normally deleted, aka 404) are tombstoned after 30 days. You can't revive them without a registry change or admin access to this very repo.
This last change actually makes the security bulletin Will once had impossible. If we remember, that one was a name takeover, possible because GitHub freed the user-/org-names after n days. But that n is > 30, so before we even get into that situation we already tombstone automatically.
Maybe I delete the other code later.