3 ms·
Right. But if you’re trying to establish an HTTPS connection to some server then that server’s cert is signed by some trusted root and THAT cert expires. Which
by jameshart 3y ago
Right. But if you’re trying to establish an HTTPS connection to some server then that server’s cert is signed by some trusted root and THAT cert expires.
Which is why it might be more future proof to embed your own non expiring cert and use an out-of-band signature verification for firmware rather than relying on being able to establish an HTTPS connection forever.
- deleted 3y ago[deleted]
- NohatCoder 3y agoYes, that is what you should do. The problem is that they don't do that. No harm in also running HTTPS on top of that as you can renew the TLS certificate without issue.
- ilyt 3y agoAt that point just use http + sigs. If you have working signature infrastructure you don't need encryption. There is some danger, attacker can see what you are getting, but that's far lower than "the update broke"