5 ms·
Ditto for “smart things” hardware. I manufacture a non internet connected wifi device, and I basically can’t use HTTPS, WebBluetooth, and a host of other thing
by randyrand 4y ago
Ditto for “smart things” hardware.
I manufacture a non internet connected wifi device, and I basically can’t use HTTPS, WebBluetooth, and a host of other things because I can’t get a long 30+ year cert anywhere. 1 year is max for the web.
Do they really prefer forcing people to use HTTP? It’s bone-headed.
At the very least, they need to make an exception for LAN devices, but they don’t.
- antoniuschan99 4y agoCan’t you do a self cert and set the expiry to 2049 or something?
- prepend 4y agoClients won’t recognize the self cert so instead of an expired cert warning, the user will get an unknown cert warning.
- nijave 4y agoThat's mainly a problem for genetir web clients, though. If it's a mobile or other app, you can package the CA in. I think web clients generally wouldn't be able to connect to an IoT device over a private or public IP anyway since afaik public CAs won't issue certs for IPs.