Repository navigation
Match the active signer policy while awaiting API 33 Play rotation - #14
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.
ConnectBot’s merged policy describes an API-28 direct rotation that the signer VM never activated. Restore the exact policy currently used by the VM, with an API-33 rotation boundary, while waiting for Google’s complete RSA-1024 → old Play key → RSA-4096 proof.
Remove the superseded direct-chain proof; keep the replacement public certificate for the pending upgrade. Revision 6 was never accepted by the auditor, so this corrects the published policy without changing the VM or restoring ledger state. The eventual combined-chain policy will use a fresh revision greater than 6.
Both Play downloads for version 11101006 contain 80 APKs with valid signatures, but only the existing RSA-1024 → old Play key lineage. The restored JSON exactly matches the active exported revision-5 policy; both profiles specify
rotation_min_sdk: 33.