- Nov 21, 2024
-
-
cyberta authored
The test also proofes that reading the appropriate environment variables work as expected on the server side. The obfsvpn client doesn't read environment variables and thus need to be invoked with the corresponding command line flags.
-
- Nov 20, 2024
-
-
cyberta authored
-
- Nov 19, 2024
- Nov 10, 2024
-
-
jkito authored
during the running of the client it might happen that there's an actual error for which we need to restart the UDP listener where openvpn send its traffic, but an error will also be encountered in the copy loop when tearing down the connection, we can filter these types of errors by checking if it is a net.ErrClosed error type and re-create the UDP listener only when the error is not a net.ErrClosed
-
- Nov 07, 2024
-
-
jkito authored
-
- Oct 04, 2024
-
- Sep 26, 2024
-
-
Maxb authored
This adds the option to use QUIC as a replacement dialer+listener for our obfs4 connection. Because we have already implemented this pattern for KCP it was relatively straightforward to add QUIC as this "inner transport". That is, our network stack looks like: ┌──────────────┐ ┌──────────────┐ │OpenVPN client│ │OpenVPN server│ └──▲───────────┘ └──▲───────────┘ │ │ │ UDP │ UDP ┌──▼───────────┐ ┌──▼───────────┐ │obfsvpn client│ │obfsvpn server│ └──▲───────────┘ └──▲───────────┘ │ │ │ │ ┌──▼─────────┐ ┌──▼───────────┐ │obfs4 dialer│ │obfs4 listener│ └──▲─────────┘ └───▲──────────┘ │ │ │ obfs4 │ obfs4 ┌─▼─────────┐ QUIC ┌──▼──────────┐ │QUIC dialer├◄───────►│QUIC listener│ └───────────┘ └─────────────┘ This makes the obfs4 layer and the QUIC layer somewhat duplicative in that they're both technically "obfuscation" layers (a censor won't see any obfs4 traffic because it's already wrapped in the QUIC layer). This commit is more of a spike to prove that QUIC can easily be swapped/added as a circumvention protocol layer/technique and the next work can be refactoring our code such that we can optionally swap the obfs4 layer entirely with our QUIC one.
-
- Sep 25, 2024
-
-
Maxb authored
-
- Sep 17, 2024
-
- Sep 03, 2024
-
-
Maxb authored
-
Maxb authored
We can easily check that the obfsvpn client will reconnect to our obfsvpn host servers by restarting the server docker containers in our integration test after the initial successful connection and then assuring that they are able to connect again after a reasonable time :)
-
- Aug 30, 2024
-
-
Maxb authored
-
- Aug 21, 2024
-
-
cyberta authored
-
- Aug 19, 2024
- Aug 16, 2024
- Aug 14, 2024
-
-
cyberta authored
-
- Aug 13, 2024
- Aug 05, 2024
-
-
power puffin authored
-
- Aug 02, 2024
-
- Jul 29, 2024
-
-
Maxb authored
-
- Jul 27, 2024
-
-
Maxb authored
-
- Jul 22, 2024
-
-
Maxb authored
-
- Jul 09, 2024
-
-
kwadronaut authored
-
kwadronaut authored
- /docker-compose.yml - /scripts/integration-test.sh
-
- Jul 07, 2024
-
-
this updates the docker-compose definition to restart the control and hop client containers only 3 times to reduce resource consumption on the gitlab ci builders
-
-
- Jun 25, 2024
-
-
cyberta authored
-
- Jun 17, 2024
- May 31, 2024
-
-
cyberta authored
-