Repository navigation
Prepare ConnectBot production signing policy for Bathysign v0.2.2 - #22
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.
Adds native-exported revision-9 signing policy for connectbot/connectbot, pinning immutable Bathysign v0.2.2 source and annotated tag object independently. The historical revision-8 policy was reproduced before export; Android profiles, certificates, lineages, receipt key and trust authority are preserved. Publishing routes main to alpha, v1.11.x to beta with existing version-code bounds, and other stable versions to alpha. The disposable v0.2.2 trial passed signing, staged verification, hosted finalization, GitHub publication and independent published-release/tamper verification for both profiles; Play was disabled in that trial. This PR stages public policy only. Production appliance, collector and Google federation remain unchanged; coordinated deployment and fresh ledger backups are still required.