Repository navigation
Verify releases against every organization a tool has lived in - #140
Merged
Merged
Conversation
download-and-verify hardcoded carabiner-dev as the place to download from and as the identity releases must carry: the build point in the provenance and the release workflow that signed it. ampel moved to policylabs, so its next release will be built and signed there and would be rejected, while every release up to v1.3.10 keeps the old identity. Add an orgs input, defaulting to "policylabs carabiner-dev". The release is downloaded from the first organization that has it, and its provenance is checked against each one in turn, build point and signer together, so a release has to be consistent with a single organization. Tools that have not moved keep verifying against carabiner-dev and need no change when they do move. Point the ampel bootstrap and its rotate script at policylabs/ampel. The pinned hashes are unchanged. Signed-off-by: Adolfo Garcia Veytia (puerco) <puerco@carabiner.dev>
miniprow
Bot
added
lgtm
Contributor
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: puerco The full list of commands accepted by this bot can be found here. DetailsApproved by a repository administrator.Approvers can indicate their approval by writing |
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.
download-and-verify hardcoded carabiner-dev as the place to download from and as the identity releases must carry: the build point in the provenance and the release workflow that signed it. ampel moved to policylabs, so its next release will be built and signed there and would be rejected, while every release up to v1.3.10 keeps the old identity.
Add an orgs input, defaulting to "policylabs carabiner-dev". The release is downloaded from the first organization that has it, and its provenance is checked against each one in turn, build point and signer together, so a release has to be consistent with a single organization. Tools that have not moved keep verifying against carabiner-dev and need no change when they do move.
Point the ampel bootstrap and its rotate script at policylabs/ampel. The pinned hashes are unchanged.