News for hackers. Stuff that matters.
Re:Chrome 68 Released: HTTP Sites Marked as “Not Secure” by colejohnson66 on Wednesday July 25, 2018 @06:20AM (#17608152)
But then what about when the printer’s IP address changes because it’s dynamic?
Re:Chrome 68 Released: HTTP Sites Marked as “Not Secure” by dspillett on Wednesday July 25, 2018 @06:35AM (#17608221)
ddns?

Or use addresses like https://192-168-1-1.hp.net (https://192-168-43-123.hp.net, https://10-20-30-40.hp.net, and so on) and a wildcard cert. No harder to document than telling people to go to http://192.168.1.1.

Though they should be more careful than to use to top-level domain as they need to include the private key in the device unless they have the devices call out to have a new certificate generated, perhaps 192-168-1-1.internaldevices.hp.net and so forth.

Re:Chrome 68 Released: HTTP Sites Marked as “Not Secure” by nsgi on Thursday July 26, 2018 @02:35PM (#17619737)
It would be necessary to use a different private key on each device for it to be secure, so something like 192-168-1-1.internaldevices1489420.hp.net
Re:Chrome 68 Released: HTTP Sites Marked as “Not Secure” by fulafel on Wednesday July 25, 2018 @08:01AM (#17608580)
DNS got fixed to handle dynamic updates in the early 2000's.