I'd like to hear how this is different from Streisand? [0] (and also Sovereign, which I see someone else posted below).
I set up Streisand on a $5/mo Digital Ocean droplet a while back and the whole family uses it on all our devices with great results. It is pretty much a 'fire and forget' solution that I haven't had to touch in over a year.
I've been using streisand for a while (from China) and it's great; the main reason I can see that you might want to use the linked project instead is that it has a lot less surface area so it could be more secure (it's a lot easier to harden/audit openvpn alone than all the services streisand includes).
That said, if I was going to pick one protocol out of the selection offered by streisand, it would be l2tp/ipsec instead of openvpn (assuming you're hosting on digital ocean. The networks on AWS and GCE are more restrictive and you can't serve l2tp/ipsec from there). I found this to be easier to set up (the client-side software is already included in most operating systems) and to have the best performance.
This project aims to "do one thing and do it well".
I posted this elsewhere but it bears repeating. This project is designed to be simple, auditable, and disposable, and have the minimum attack surface and maintenance costs.
Other tools are great, but the cost of swapping certificates and IP addresses and zone files can weigh you down.
Streisand would do well to have numerous playbooks that remix roles for smaller services (if they don't already).
I have a VPS and I use it for webhosting for myself and some friends. I've thought about (in some cases tried) and then decided against setting up my own mail server, my own irc bouncer, my own xmpp server and my own cloud storage. Each time, the killer was basically "I could do this, but it would take too long to figure out and it would probably not be super secure at the end.
At the very least, a project like Sovereign (written using something as declarative and idempotent as Ansible) would be great to look through and see how it manages certain things.
And that doesn't detract from your project, OP - I like that your focus is tight and your setup instructions detailed. I'm far more likely to actually try installing a small project like yours than a behemoth that will change who knows what throughout my system.
last time I set up an openvpn server on digitalocean without `tun-ipv6`, it leaked my ISP's ipv6 address to the internet while my ipv4 address was correct (a digitalocean address). disabling ipv6 on a vpn by default doesn't make a lot of sense to me if the intention is a layer of privacy around your ISP.
Hi, thanks for your feedback. Can you submit a github issue? I need to establish a traffic testing method for assessing whether any traffic is leaking. This would be a valuable general tool for all vpn toolchains.
I'd like to see some hardening of the box if it's going to be used as a VPN server. My boxes in the DO IP range routinely get targeted by malicious traffic from China and Russia.
This tool is to protect you from verizon supercookies and comcast deep packet inspection. These companies sell access to this data to local law enforcement without requiring a warrant. LEO make choices based on the narrative about you they can build. We need to protect ourselves from people who would do us harm in clever and careful ways.
Depending on your threat model it's perfectly fine. It won't work against a nation-state-level adversary, but I don't get the feeling it's meant to. Against opportunistic passive sniffing or active MitM in cafés and such it's adequate.
[+] [-] cyberferret|9 years ago|reply
I set up Streisand on a $5/mo Digital Ocean droplet a while back and the whole family uses it on all our devices with great results. It is pretty much a 'fire and forget' solution that I haven't had to touch in over a year.
[0] - https://github.com/jlund/streisand
[+] [-] bdarnell|9 years ago|reply
That said, if I was going to pick one protocol out of the selection offered by streisand, it would be l2tp/ipsec instead of openvpn (assuming you're hosting on digital ocean. The networks on AWS and GCE are more restrictive and you can't serve l2tp/ipsec from there). I found this to be easier to set up (the client-side software is already included in most operating systems) and to have the best performance.
[+] [-] robbintt|9 years ago|reply
I posted this elsewhere but it bears repeating. This project is designed to be simple, auditable, and disposable, and have the minimum attack surface and maintenance costs.
Other tools are great, but the cost of swapping certificates and IP addresses and zone files can weigh you down.
Streisand would do well to have numerous playbooks that remix roles for smaller services (if they don't already).
[+] [-] cylinder|9 years ago|reply
[+] [-] rosser|9 years ago|reply
Both even use Ansible.
[+] [-] NickBusey|9 years ago|reply
[+] [-] mos_basik|9 years ago|reply
I have a VPS and I use it for webhosting for myself and some friends. I've thought about (in some cases tried) and then decided against setting up my own mail server, my own irc bouncer, my own xmpp server and my own cloud storage. Each time, the killer was basically "I could do this, but it would take too long to figure out and it would probably not be super secure at the end.
At the very least, a project like Sovereign (written using something as declarative and idempotent as Ansible) would be great to look through and see how it manages certain things.
And that doesn't detract from your project, OP - I like that your focus is tight and your setup instructions detailed. I'm far more likely to actually try installing a small project like yours than a behemoth that will change who knows what throughout my system.
[+] [-] tlrobinson|9 years ago|reply
I'd be interested in something like this with a strong focus on security.
[+] [-] tribby|9 years ago|reply
last time I set up an openvpn server on digitalocean without `tun-ipv6`, it leaked my ISP's ipv6 address to the internet while my ipv4 address was correct (a digitalocean address). disabling ipv6 on a vpn by default doesn't make a lot of sense to me if the intention is a layer of privacy around your ISP.
[+] [-] robbintt|9 years ago|reply
[+] [-] jwilk|9 years ago|reply
[+] [-] tedmiston|9 years ago|reply
[+] [-] robbintt|9 years ago|reply
[+] [-] andreareina|9 years ago|reply
[+] [-] lucasjans|9 years ago|reply
[+] [-] wstrange|9 years ago|reply
[+] [-] robbintt|9 years ago|reply
[+] [-] caspereeko|9 years ago|reply
[+] [-] jlgaddis|9 years ago|reply
[+] [-] vxNsr|9 years ago|reply
[+] [-] cabalamat|9 years ago|reply
[+] [-] insubstantive|9 years ago|reply
[+] [-] andreareina|9 years ago|reply
[+] [-] eeZah7Ux|9 years ago|reply
[+] [-] scoot|9 years ago|reply
[+] [-] necessity|9 years ago|reply
[+] [-] dstryr|9 years ago|reply
[+] [-] JonoBB|9 years ago|reply