We have successfully completed our migration to RAM-only VPN infrastructure - Mullvad VPN
We have successfully completed our migration to RAM-only VPN infrastructure - Mullvad VPN
Today we announce that we have completely removed all traces of disks being used by our VPN infrastructure!
You're viewing a single thread.
I do not use a VPN provider but damn, that's cool as hell. Now how do I self host it? :D
Wouldn't that defeat the purpose of a VPN?
Not if you want to VPN to your home.
But why would logs you hurt than?
How to debug and how to do forensic if only the supposed persons are connected to your home, if you don't have any logs?
VPNs prevent your origin ISP from keeping logs; you may not want your office, school, coffee shop, city wifi, etc. to know which services you're accessing.
You can (should) still require identification on your home hosted services, you can log that.
Just run wireguard on a ram only vm at your home
You already are. It's called using your own connection. You don't need to be your own middleman, shuffling data to/from yourself.
Self hosting would essentially just be using a ramdisk. If you want to be crazy about it, you could even run a VM with its storage entirely within a ramdisk.
Note that the lack of logging probably doesn't matter when your self-hosting, since it's all for you.
Concept of RAM only Linux images with validation and signing is something seen in some datacenters. For example, Lenovo has this in their confluent cluster management (https://hpc.lenovo.com/). A node can network boot or boot from usb (read-only) and all writes go to RAM.
Alternatively, booting a LiveCD amounts to the same thing without requiring a boot server, you have a local 'disk' but nothing writes to it. If extra paranoid you could actually boot it from a burned DVD, but in practice even when booting from USB most 'live' images only write filesystem to RAM.