Repository navigation
feat: support imported and bundled HTTPS signing CAs - #58
Merged
Merged
Conversation
fython
force-pushed
the
feat/https-signing-ca
branch
from
November 14, 2026 12:06
05639ed to
6e3cd5e
Compare
Add a mitmproxy-style signing CA pipeline to the local HTTPS server, and feed it from CI: - Import a CA chain plus its private key at runtime, or bundle a combined PEM at build time through WHEELPLAY_HTTPS_CA_PEM / .local/https-ca/emudhra-ca.pem. - Provision the bundled CA from the WHEELPLAY_HTTPS_CA_PEM_BASE64 Actions secret. Material is written under RUNNER_TEMP, validated against the same rules as BundleHttpsCa, and deleted when the step or job ends. - Default the bundled source to the pinned mitmproxy commit when the secret is absent (WHEELPLAY_HTTPS_CA_FALLBACK=mitmproxy), require a CA by default (WHEELPLAY_HTTPS_CA_REQUIRED=1), and mark such artifacts with -MITMPROXY-CA. - Cover both the Release and Debug workflows, with the Debug build exporting the CA path through GITHUB_ENV and reusing it from build-signed-android.sh. Docs: docs/HTTPS_SIGNING_CA.md and docs/RELEASE_SIGNING.md.
fython
force-pushed
the
feat/https-signing-ca
branch
from
November 14, 2026 12:10
6e3cd5e to
73fb737
Compare
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.
WheelPlay can now issue HTTPS server certificates for its current LAN/Tesla access IPs and Web hostname using a supplied RSA or EC signing CA, following mitmproxy's CA-loading flow.
WHEELPLAY_HTTPS_CA_PEMor.local/https-ca/emudhra-ca.pem. Only the specified file is staged, and removing the configuration clears stale generated assets./tls.json.WheelPlayActivityand settings; add translations, documentation, and synthetic-CA tests. No vendor certificate or private key is committed.Validation on commit
05639ed, based on currentmain: all 41 targeted tests passed (SigningCaTest,LanTlsTest,LanTlsEcTest,HttpsSettingsUiTest, andWebListenSettingsTest), and:mobile:assembleDebugpassed. Localization andgit diff --checkalso pass. Packaging checks verified that the APK contains the exact configured synthetic PEM, excludes unrelated files, and removes the PEM after configuration is cleared.Real eMudhra material and head-unit behavior have not been tested. Generated leaf certificates last at most seven days and renew on service restart or access-setting changes; there is no scheduled renewal.