Repository navigation
Vouch for the app's signing keys, so its links open it - #106
Merged
Merged
Conversation
The site now answers /.well-known/assetlinks.json with com.gridpointcode and the keys it may be signed with: the three Google holds for the app, as Play Console's Android developer verification lists them, the app signing key among them, and the upload key, so a release signed here and installed by hand verifies too. Until now the file was an empty list, and a link to gridpointcode.com/play opened in the browser. audit/assetlinks.py passes: the site vouches for com.gridpointcode signed with four keys, and the app's manifest asks it to. The README's note that verified links waited for the key moves out of Not here yet, and PLAY.md's checklist marks the step done.
Play signs a new app with quantum-ready hybrid signing: a classical key for devices before Android 17, and a classical and a post-quantum key together from Android 17. All three are app signing keys, which is why Android developer verification lists three, and Google's help asks for all three in assetlinks.json, as the file already has them. The README and PLAY.md now say so, and give the page Play Console shows them on.
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.
Turns on verified links. A link to
https://gridpointcode.com/playopens the Android app directly, instead of the browser.What changes
web/public/.well-known/assetlinks.jsonwas an empty list. It now namescom.gridpointcodeand four SHA-256 fingerprints:81:FA:A3:B1:…:E6:BD:A9F5:DF:36:39:…:C5:00:652B:FF:F9:E7:…:05:EE:A0DB:42:9E:40:…:B0:70:A8:C5Play signs a new app with quantum-ready hybrid signing, so it has three app signing keys: a classical one for devices before Android 17, and from Android 17 a classical and a post-quantum one signing together. Google's help asks for all three in
assetlinks.json. Android developer verification lists the same three, and Play Console shows them under Protected with Play, Play Store distribution, Play app signing. None of them is the upload key or this machine's debug key.Checks
audit/assetlinks.py: "the site vouches for com.gridpointcode signed with 4 keys, and the app asks it to". Its unit tests pass.audit/markdown.pypasses.After it deploys
The Pages workflow deploys on any change under
web/. Once it's live, uninstall the app, reinstall it from the Play internal test, and run:It should say
verifiedforgridpointcode.com. A device that checked while the file was empty keeps that answer until the app is reinstalled.