3 ms·
For all those that scream about local devices and HTTPS: if you really want HTTPS (and your printer/router supports HTTPS) you can get a certificate very easily
by alanfranzoni 8y ago
For all those that scream about local devices and HTTPS: if you really want HTTPS (and your printer/router supports HTTPS) you can get a certificate very easily from let's encrypt:
- create an "internal" domain for your lan, e.g. home.example.com
- make AWS Route53 handle that zone
- create some AWS IAM credentials for Route53
- create some hosts (e.g. router.home.example.com)
- use certbot with the route53 dns option to get a certificate and private key. Certbot will automagically add some TXT records to verify hostname ownership and provide you with that.
NO NEED to expose anything on your public IPs, but mind you: your hostname will appear in public CT logs. No "greatnascontainingmypartnersnudephotos.home.example.com" hostnames!
- swiley 8y agoThis requires the device to be connected to the internet often which isn’t always the case. If the device is the gateway you now have a circular dependency (one that will only cause problems rarely but it’s still there.) As long as http still works it’s fine, I think a security warning about it is probably a good thing, but there definitely are places where “just use let’s encrypt” isn’t an acceptable solution.