Repository navigation
Authorize Bathysign v0.2.0 disposable test - #19
Merged
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
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.
Authorize the isolated
connectbot/test-signer-1v0.2.0 signing/finalization trial before the production ConnectBot cutover.Adds native-exported revision 13 under
.github/bathysign/1421097317.jsonwith exact immutable release tagv0.2.0and commit2103fdfc57058d232be05e2a16697a8e90e6b85ffor the trusted attestor/finalizer. The test signing profiles, key identities, receipt certificate and rotation lineage match the existing historical test policy. The separate publishing configuration explicitly disables Google Play.The trial uses a separate loopback-only QEMU guest, test keys disjoint from production, and a migrated copy of the test ledger. Production configuration, VM 134, collectors, policy and Google federation are unchanged. Existing historical policy files remain available.
Validation: native v0.2.0 policy export using test keys; hosted verifier schema/certificate validation; exact profile and receipt identity comparison to the old test policy; isolated guest readiness with authenticated TUF refresh; no findings from the policy checkout audit.
The policy files must be available on protected main for the finalizer to run. This PR changes only the disposable repository's policy.