4 ms·
Most home broadband users don't have domains and would be unlikely to want to pay for one, just to remote login to their router.
by rythie 9y ago
Most home broadband users don't have domains and would be unlikely to want to pay for one, just to remote login to their router.
- Aaargh20318 9y agoLet's Encrypt supports wildcard certificates (since a couple of days ago), you could automate it.
- rythie 9y agoAutomate what exactly? the point is most home users access their router with 192.168.0.1, they don't have a domain name, nor are they likely to want to buy one. This is now no longer a niche thing that a few people want to do, it's a 100s millions (if not a billion) of households needing to do this to access their own router, so it doesn't say "not secure".
- Aaargh20318 9y agoEvery internet-connected device should have a FQDN, that's just common sense.
- forgottenpass 9y agoShould? Yes. I can get on board with this. A ridiculous proposition given the current state of technology? Also yes. If it happens, implemented in turnkey devices (such as SOHO routers) in a way that enhances vendor control rather than empowering home users with the option to use their own domain names and certs? Likely, that's the trend these days and doesn't show signs of receding. The last line is kinda a tangent, but if that came to be the case, I would no longer be on board with the idea every device should have a FQDN.
- nileshtrivedi 9y agoSource? Their blog post had mentioned 27th Feb as the date for wildcard support in production.