Repository navigation
Authorize the combined Play signing history on API 33 - #15
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.
Activate ConnectBot’s developer-controlled RSA-4096 APK key on API 33+, preserving RSA-1024 signing on API 24–32. Both google and oss profiles use Google’s complete RSA-1024 → old Play key → RSA-4096-2026 history, extracted unchanged from Play-generated APKs for version 11101009.
The lineage SHA-256 is
cc39d1eebcec803f3b42116eba8d2cf88d7ba150adc9235309f596be443c8955; all three certificates retain capabilities 23, without rollback. The new certificate matches the previously published replacement. Upload, transparency and receipt keys and the measured signer revision remain unchanged. Policy revision 7 skips the never-activated revision-6 proposal.Validation: all 80 downloaded APKs verify with the expected complete ancestry; the base APK verifies with RSA-1024 on APIs 24/27/28/32 and RSA-4096 on APIs 33/36/37. The native administrator independently verifies/imports the proof and validates the offline candidate, with the policy hash checked against the native exporter. Policy scans found no secrets, debug artifacts or TODOs.
The candidate is staged separately on Proxmox; active configuration remains revision 5. After review/merge, activate revision 7 and verify auditor acceptance and a fresh GitHub signing flow. F-Droid’s separate signing history is not changed by this policy.