Age | Commit message (Collapse) | Author |
|
3a674d30e1c7118b73efaf353cea7c43a95dc8c7, fixes possible race condition between DeviceStateReceiver and OpenVpnManagementThread, which results in incorrect LEVEL_NONETWORK state
|
|
|
|
properties there
|
|
ConfigHelper, use injection pattern for these helpers
|
|
(re-)started
|
|
laggyness of the UI noticably
|
|
|
|
in persisted openvpn config. The private key is stored encrypted instead
|
|
relevant commits: 5e7b841c8d5111e6b63e74944903a168939ca723 a6de5a9e4d8d757414c5e2f94eb806be9216dda3 9e704d04dc7f2f93bddf85d371772340fa5af0b1 4466103d770c353cfb8d4ea08093560ba28d58b8 b9ac2b15eac3e5e5f9dc89c948ec8278e2e7c1f9 3cb8f44a92471e43589a80067380d7b262c18c20)
|
|
|
|
|
|
|
|
and 'kcp' become valid protocols for obfs4
|
|
|
|
|
|
as part of this gombile JNI generation fix
|
|
|
|
|
|
gateway selection UI all pluggable transports flavors will be summed up and handled the same way. A gateway can support both obfs4 and the kcp flavor.
|
|
|
|
which can be mocked for testing
|
|
|
|
|
|
|
|
|
|
|
|
deprected and unused
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
fallback
|
|
|
|
* fix setting http proxy port correctly
* snowflake+tor does currently only work when being connected to a wifi, not a cellular network.
For now, we check if the device is connected to a wifi, before attempting to start tor
|
|
|
|
|
|
|
|
of the LogView
|
|
* always use a bound service connection to start a vpn service as foreground service to fix remote excptions. These appeared if the system wasn't able to set the service as forground shortly after it was started
* move vpn start logic from LaunchVPN activity to EIP service. LaunchVPN/VoidVPNLauncher is only used in case we need to ask the user for a permission. It reduces visual glitches when the transparent LaunchVPN activity appears and disappears
|
|
|
|
foreground service start
|
|
notification in onCreate already
|
|
|
|
reboot due to always-on system settings or if system killed app due to low memory
|
|
negotiation issues
|