I ran across this one today: https://github.com/trailofbits/algo
Based on ipsec, so no extra software to install on the clients. Looked interesting.
How to build your own VPN if you're wary of commercial options
41–50 of 117 posts
Re: How to build your own VPN if you're wary of commercial options
#42Earlier quoted context omitted.
Or Streisand.[0] 0) https://github.com/jlund/streisand
Most people who have an opinion between the two suggest algo is the better of them, for what its worth.
Thanks. I've never used either, actually. I just do it manually. Another good option for AWS is OpenVPN Access Server. There's a template.
Re: How to build your own VPN if you're wary of commercial options
#43Earlier quoted context omitted.
> AWS instance is easily traced back to you. Define "easily" as used in this context. Easy is a product of whom your enemy is. Is your enemy your ISP? If that's the case, I don't think it's "easy" for them; they would have to pay Digital Ocean or Amazon to get your data, and probably isn't really that valuable to them. Is your enemy the MPAA? If that's the case, I still don't think it's particularly "easy" for them.…
The MPAA will serve an automated DMCA notice to your VPS provider, who will terminate your account at the very least.
Amazon's not in the business of terminating accounts the second a copyright request comes in. They want to build trust with their customers that they won't just turn you off on a whim.
Re: How to build your own VPN if you're wary of commercial options
#44Earlier quoted context omitted.
The MPAA will serve an automated DMCA notice to your VPS provider, who will terminate your account at the very least.
Amazon's not in the business of terminating accounts the second a copyright request comes in. They want to build trust with their customers that they won't just turn you off on a whim.
Re: How to build your own VPN if you're wary of commercial options
#45Earlier quoted context omitted.
Exactly. The author says because hosting companies are big they would never give information but this is a complete flaw. Google and Reddit are both known to hand information to law enforcement. Companies like digital ocean don't put as high as emphasis on customer privacy as companies likes PIA. On 90% of the service portals for servers I've purchased have had a message showing my IP was logged for safety reasons. S…
Put your consideration in Germany, privacy is pretty enforced here.
GEMA is pretty aggressive in Germany. Talking jane random and they don't do file sharing because they are in fear of GEMA.
Re: How to build your own VPN if you're wary of commercial options
#46The problem with a home-grown VPN is that you lose some of the plausible deniability that's gained from a shared VPN. If you have a VPN connected to a privately-owned AWS instance, the IP coming from that AWS instance is easily traced back to you. Whereas if your external IP is coming from a cluster that is shared by thousands of other people using that VPN, it is more difficult for someone to tie that specifically b…
There are use cases that make sense. My home linux router intercepts and sends all DNS and NTP requests, then routes all DNS requests to multiple VPS nodes that in turn, use multiple DNS recursors at each VPS datacenter. I intentionally avoid google and opendns. I override the min-ttl of all requests to avoid some shenanigans and I am well aware of the issues this can cause. At a minimum, my ISP can not see or tamper…
That's really cool. Do you have links to share about that setup?
Re: How to build your own VPN if you're wary of commercial options
#47I'm surprised that tinc-vpn.org isn't mentioned more in these VPN threads. It's such a pleasure to work with when compared to OpenVPN. You can standup a distributed mesh VPN in minutes.
Re: How to build your own VPN if you're wary of commercial options
#48We also built a solution to quickly deploy your own VPN using OpenVPN: https://www.tinfoilsecurity.com/vpn
All open-source, too.
Re: How to build your own VPN if you're wary of commercial options
#49Earlier quoted context omitted.
Amazon's not in the business of terminating accounts the second a copyright request comes in. They want to build trust with their customers that they won't just turn you off on a whim.
https://forums.aws.amazon.com/thread.jspa?messageID=399950
That's their official response, and rightly so it should be. Talking from experience, I've had many requests for different websites I run and almost all were frivolous. Some content I took down anyways, and some I explained to Amazon why it was frivolous. They've never cancelled any of my services or even threatened to.
Re: How to build your own VPN if you're wary of commercial options
#50I would like to have a setup like this: - One VPN to connect laptop on the road with machines at home LAN, and with VM:s on different hosts. - Have this VPN "exit" via a commercial VPN-provider (for privacy). Could I easily configure this? Have one of the VM's be the VPN server and configure it to "exit" trough the commercial VPN? I haven't really managed / configured "real" VPN's, how does local access work? I.e, wh…
> Could I easily configure this? Have one of the VM's be the VPN server and configure it to "exit" trough the commercial VPN? This is easily doable, but it comes down to how much you trust your commercial VPN host. As it is, most of these service providers are pretty shady to say the least. If it were somehow possible to provide a service that is provably secure and log free, that would be a different story.
For the last year or something I have been using https://www.ovpn.com/en. They are not shady at all, and allow bitcoin or cash payments, and are run by a friend of a friend, so I trust them. But no less provably secure compared to the rest.