Live data from Hacker News

Free Open Source VPN – AES 256 – WireGuard and OpenVPN

openinternetaccess.com

1–10 of 15 posts

Re: Free Open Source VPN – AES 256 – WireGuard and OpenVPN

#4
post #2

It's as if everyone here suddenly forgot all free VPNs are honeypots.

And free software comes with backdoor? You're right in thst the reputation is mostly accurate but there are a few that offer a free and a paid tier (protonvpn for example)

Re: Free Open Source VPN – AES 256 – WireGuard and OpenVPN

#6
post #3
post #2

It's as if everyone here suddenly forgot all free VPNs are honeypots.

Do you have a VPN you do recommend?

Get a cheap VPS and setup one yourself.

There are plenty of guides, especially for the big VPS providers like DigitalOcean.

Re: Free Open Source VPN – AES 256 – WireGuard and OpenVPN

#7
post #2

It's as if everyone here suddenly forgot all free VPNs are honeypots.

The biggest honeypots are the paid VPNs....

They have your payment information, identity, and everything all linked to that VPN config.

Don't be fooled by the standard cliche around free VPNs. Some free VPNs are bad, but to say that because a VPN is paid it is legit is just wrong.

Re: Free Open Source VPN – AES 256 – WireGuard and OpenVPN

#8
post #2

It's as if everyone here suddenly forgot all free VPNs are honeypots.

The biggest honeypots are the paid VPNs.... They have your payment information, identity, and everything all linked to that VPN config. Don't be fooled by the standard cliche around free VPNs. Some free VPNs are bad, but to say that because a VPN is paid it is legit is just wrong.

You can send Mullvad.net an envelope with cash for an anonymous VPN account. Just make sure to wear gloves when sealing the envelope. ;-)

Re: Free Open Source VPN – AES 256 – WireGuard and OpenVPN

#10
The OpenVPN configuration uses AES-128-GCM as the cipher, which itself is fine but the website claims it is using AES-256.

More concerning is the 'Tor VPN' and bridge being offered. The Tor bridge here is not a proper bridge, instead the SOCKS port is being exposed on a public IP rather than the usual 127.0.0.1. SOCKS is an unencrypted protocol so everything being sent to the bridge is exposed on the wire, and your ISP can trivially see that you are connecting to a VPN over it. This is dangerous and misleading - Tor even warns you that the protocol is not encrypted when you expose the SOCKS port publicly. Real Tor bridges are simply relays not listed in the consensus file. Connections using them are still encrypted using TLS. The website incorrectly claims that by using the VPN over Tor configuration files, you are masking your VPN connection from your ISP.

This free VPN is so misleading that I felt the need to make a HN account just to write about it.

Post reply on HN