Add Proton VPN WireGuard provider - #720
Draft
kasnder wants to merge 1 commit into
Draft
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
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.
Summary
This adds an isolated Proton VPN provider boundary for evaluating Proton account login and WireGuard profile refresh support alongside the existing Mullvad path.
Included
Validation
:app:compileGithubDebugKotlin:app:testGithubDebugUnitTest --tests 'net.kollnig.missioncontrol.wg.proton.*'Follow-up before production
This is intentionally provider-layer work only. Production integration still needs encrypted session persistence, login/settings UI, client key generation, and wiring refresh callbacks into
WgEgress. Full native APK assembly was not run because the local NDK installation is incomplete.