or use docker: https://hub.docker.com/r/kylemanna/openvpn/
How to build your own VPN if you're wary of commercial options
11–20 of 117 posts
Re: How to build your own VPN if you're wary of commercial options
#12Like, I'm not sure why anyone thinks that: 1. AWS, DO or Linode won't respond to a subpoena 2. That any of those three won't have extensive logging in place, without the privacy goals that a VPN provider would have You're just switching your ISP to AWS when you do this, which might be better than what you've got, but certainly isn't flawless untraceable security
AWS/DO/Linode arn't trying to monetize and manipulate their outbound traffic as aggressively as Consumer ISP's are.
These private VPN solutions simply protect all your traffic from ISP interference.
Re: How to build your own VPN if you're wary of commercial options
#13or use docker: https://hub.docker.com/r/kylemanna/openvpn/
> or use docker: https://hub.docker.com/r/kylemanna/openvpn/
That's my project, thanks for the shout out!
For those curious the main feature of the Docker container is to wrap up the PKI generation and conf file generation for the 90% use case.
Re: How to build your own VPN if you're wary of commercial options
#14This might be a good idea for a startup where they create a plug and play service so users do not have to go through all of this.
Re: How to build your own VPN if you're wary of commercial options
#15The 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…
[deleted]
Re: How to build your own VPN if you're wary of commercial options
#16Like, I'm not sure why anyone thinks that: 1. AWS, DO or Linode won't respond to a subpoena 2. That any of those three won't have extensive logging in place, without the privacy goals that a VPN provider would have You're just switching your ISP to AWS when you do this, which might be better than what you've got, but certainly isn't flawless untraceable security
I'm not sure where the claim of "untraceable security" came from.
I do something similar to this. The goal isn't avoiding legal liability or based on the belief that AWS, et al are friendly.
There are multiple reasons, but the single biggest is to thwart last-mile surveillance by my ISP. That alone is worth $10/mo and a few minutes of setup.
Re: How to build your own VPN if you're wary of commercial options
#17Like, I'm not sure why anyone thinks that: 1. AWS, DO or Linode won't respond to a subpoena 2. That any of those three won't have extensive logging in place, without the privacy goals that a VPN provider would have You're just switching your ISP to AWS when you do this, which might be better than what you've got, but certainly isn't flawless untraceable security
I really hope people aren't using a VPN for untraceable security. VPNs are for privacy, not for getting away with illegal things.
Re: How to build your own VPN if you're wary of commercial options
#18The 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…
>The problem with a home-grown VPN is that you lose some of the plausible deniability that's gained from a shared VPN.
Yes, but what good is a VPN where you cannot trust your own network? I would have zero trust in any closed source private VPN. There are ways to gain anonymity from your host that wont require setting up a MITM attack vector for your traffic.
Re: How to build your own VPN if you're wary of commercial options
#19The 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…
Would it be possible to run a commercial vpn inside a hosted vpn? Still seems traceable to me...
Re: How to build your own VPN if you're wary of commercial options
#20I 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.