328 sats \ 3 replies \ @orangecrush 12 Jan \ on: Privacy Pub 1 - Buy a VPN with Bitcoin + Firewalls privacy
When you mix VPN providers through multiple nested sys-vpn qubes on Qubes-os 4.1 using qubes-tunnel, you can reduce counterparty risk from any single provider.
I have found that i make use of many of Proton+ bag of features: custom email, e2e email encryption, mail bridge for running your own email client, VPN -secure core. As always, use your own locally-generated encryption keys for storing files in the cloud. No one is worthy of your trust; keep your secrets your own.
Interesting. Do you suffer any latency issues doing that with various VPN layers? I imagine it’s still far superior to Tor?
reply
I created a minimal Debian template (1vCPU, 700MB RAM) to run the sys-vpn instances. That helps with system performance. Yes, nesting can reduce performance compared to a single VPN tunnel and yes it still far outperforms TOR.
I use different sys-vpn chains for different app qubes depending on performance and privacy needs. I try to create a tree and branch structure so that normie and secure traffic have different in-points, out-points, and mid-points with some common bi-directional trunks to confound traffic fingerprinting attacks on privacy. Working on scripting more dynamic re-assembly of inter sys-vpn pathways. In general, all providers I have used have accepted multiple concurrent connections to many individual servers.
Maybe I’ll write something up for a SN post one of these days.
reply
You definitely definitely should. Please @ me in the post when you do.
reply