If you can't see your VPN's source code, you can almost safely assume that they're broken in some way.

> If you can't see your VPN's source code, you can almost safely assume that they're broken in some way.

This is definitely true insofar that you better be able to see client code. That said, since you cannot see what the server is running, even if they release their code, you will still end up with a trust actor or two (vpn operator or sometimes multiple vpn operators in double hop cases).

That’s exactly the reason we introduced deterministic and verifiable VPN technology on https://VP.NET which allows you to actually see the code the VPN servers are running. Instead of trust in a non deterministic human actor you can now trust deterministic and verifiable code.

It is the end of privacy theater!

[1] I am a co-founder of VP.NET

Even if you could, there's no way to guarantee it's the same code that's actually pushing your packets around.

Even vp.net which says they use SGX to verify the code that is running on a box... yea you are verifying a box, somewhere, not necessarily the one forwarding your packets. And those packets can still be monitored/modified outside the system at some other part of the network anyways.

And even if you could verify all that, eBPF swoops in and lets you modify code at runtime with no evidence trails.

If you can see it you can also almost safely assume it’s broken in some way.