Re:Please log in with router's password
by closeparen on Tuesday August 10, 2021 @08:22PM
(#28136482)
Why is exposing a web service considered so much worse than exposing a VPN service? WireGuard is respected for low complexity and high quality, sure, but what prevents a web server from having the same characteristics? And there are plenty of VPN services whose huge public surfaces turned out to be vulnerable, why is running one of these any less crazy than running nginx?
[ Parent
| on HN ]
Re:Please log in with router's password
by code_duck on Wednesday August 11, 2021 @12:01AM
(#28137869)
One problem is the software on the router is likely to be outdated and vulnerable, and upgrades are not under your control.
Re:Please log in with router's password
by closeparen on Wednesday August 11, 2021 @01:25AM
(#28138341)
Isn't that equally as true of a VPN service as of a web service?
Re:Please log in with router's password
by code_duck on Wednesday August 11, 2021 @03:28AM
(#28139091)
The issue at hand is which hardware device is exposed to the external network, not which software.
Re:Please log in with router's password
by SturgeonsLaw on Wednesday August 11, 2021 @04:45AM
(#28139571)
I would (and do) place more trust in a battle-hardened VPN than a router web interface that's designed for local access.
Additionally, Wireguard (to pick a favourite) listens for connections on a specific port, and only opens a tunnel if it's presented with the correct string, otherwise it's completely silent, an attacker wouldn't even know it was there. These routers are presenting a full web server and the web UI to an attacker.