3 ms·
That's one of the reasons I'm on a VPN right now. I'm at a rental place, and the owner is reasonably competent technically (ex-DEC engineer - we have some good
by notacoward 11y ago
That's one of the reasons I'm on a VPN right now. I'm at a rental place, and the owner is reasonably competent technically (ex-DEC engineer - we have some good chats), but I still don't trust that his router is 100% safe. Come to think of it, I don't trust that mine is. Maybe I should start using a VPN even while I'm at home. Unfortunately, this can introduce a few problems of its own.
(1) You have to trust the VPN provider. Not a big problem in this case, but worth mentioning.
(2) If you have to be on your work VPN as well, you're going to have a bad time. Being only on the work VPN often isn't an option, as a lot of personal use might run into blocks and/or violate the company's policy on use of their resources.
(3) Some sites block VPNs, either intentionally or unintentionally. Just yesterday I noticed that Tumblr is blocking most (but not all) of my VPN's connection points. It's probably just an overzealous anti-DOS system rather than a deliberate block, but the effect is the same.
We really do need a better solution here. Jeff's right that home routers are a huge vulnerability. DNS and BGP hijinks are too effective and well known to leave them unaddressed any longer, and there are other issues that need to be solved as well.
- revelation 11y agoYou can eliminate 1 by self-hosting your VPN and possibly 2 with some configuration magic to have the work stuff accessible from your own VPN. 3 is actually a bit of a problem, AWS IP ranges are notorious for being widely banned.