.git_allowed_signers: Add explicit local verification method for SSH-key-based sigs. #51
+14
−0
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
…key-based sigs. Without this file, the verification for commits depends solely on keys uploaded through hosting platform UIs. The action to declare trusted keys is also made into an explicit action on the repository. Ideally, this would belong in a separate repository containing trusted maintainer identities in general. This could in the future include hosting-platform-provided identities, auto-generated, but for verification and historical records we should keep this separate.
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.
.git_allowed_signers: Add explicit local verification method for SSH-key-based sigs.
Without this file, the verification for commits depends solely on keys uploaded through hosting platform UIs. The action to declare trusted keys is also made into an explicit action on the repository.
Ideally, this would belong in a separate repository containing trusted maintainer identities in general. This could in the future include hosting-platform-provided identities, auto-generated, but for verification and historical records we should keep this separate.