3 ms·
What is the HTTPS/security solution for devices on a home/office LAN? They aren't externally accessible, don't have a globally unique name, but do have access
by rogerbinns 11y ago
What is the HTTPS/security solution for devices on a home/office LAN? They aren't externally accessible, don't have a globally unique name, but do have access to valuable content (think your router, baby camera, lighting controller, NAS, media device).
Having to teach users that you always see the padlock when accessing your valuable information over the Internet, but do not see it when accessing your even more valuable information on the LAN doesn't seem good.
- pfg 11y agoOffice setups: Deploy an internal root CA (possibly with appropriate name constraints, to limit the damage to internal domains if your CA key is compromised). Active Directory makes it relatively easy to do this. Tooling will hopefully get better now that browsers are pretty much set on going HTTPS-only. Some consumer devices could probably implement something similar to what Plex did to deploy TLS [1]. I do agree that the industry isn't where it should be yet, but hopefully everyone's feeling the pressure now. :) [1]: https://blog.filippo.io/how-plex-is-doing-https-for-all-its-users/ https://blog.filippo.io/how-plex-is-doing-https-for-all-its-...
- rogerbinns 11y agoYour office setup only works for the larger ones. And then for Windows machines that are actively managed. It doesn't for example address a BYOD iPhone. The Plex solution looks good. I wonder if lets encrypt could provide a similar solution that works for everyone, rather than products having to reimplement what Plex already did.