obfs4: stop obfs4 client and proxy in a go routine
- Aug 03, 2024
-
-
jkito authored -
jkito authored
since obfs4 and kcp is disabled in the UI when provider is riseup, transport needs to be set to openvpn to work around config file with Obfs4 and KCP set to true from a previous version of the app
-
jkito authored
riseup currently is not having any deployed obfs4 or kcp bridges but the eip-service.json contains transports[].type as obfs4 for many of the gateways, therfore the bridge options are explicitly disabled if the provider name is 'riseup'
-
jkito authored
this prevents starting openvpn connection automatically after app start, since currently there's no preference setting for it to allow the user to control the behavior this also sets DisableAutostart to true since it is currently not working on any of the platforms
-
jkito authored
this uses the contentItem property of RoundButton to use an Image item and set the power button as on/off changing from Icon to Image allows to use the mipmap property, which should improve the image quality
-
jkito authored
the Stop is blocking and cannot be called concurrently with Start, when for some reason obfs4 client fails to connect and has not yet returned from Start, a call to Stop will block until Start has returned, which makes UI unresponsive for some time calling it in a separate Go routine works around this issue as we can proceed to stop the openvpn process
-
in case of KCP the transport.Type is still obfs4, but it has a different port than obfs4, without this commit KCP enabled bridges were also considered as valid obfs4 bridges in theory the same bridge can be running in both obfs4 and KCP mode and listening on different ports, but the eip-service.json schema separates this into different transport objects this fixes a bug where after selecting obfs4 transport it was trying connect to a KCP enabled bridge with plain obfs4 mode
-
-
