Re:Chrome 68 will mark all HTTP sites as “not secure”
by collinmanderson on Friday February 09, 2018 @12:00PM
(#16341823)
The only way I see to do it the "right way" for the masses is to have the lightbulb phone-home to the manufacturer. It's a little silly, but an IoT lightbulb is silly in the first place.
[ Parent
| on HN ]
Re:Chrome 68 will mark all HTTP sites as “not secure”
by josefx on Saturday February 10, 2018 @05:35AM
(#16346740)
Ah the fridge as a service model. Instead of buying something that just works for decades you now get to pay service fees to keep some remote server online. Oh wait the company just went under and nobody can host trusted replacement servers, guess I need a new fridge.
Re:Chrome 68 will mark all HTTP sites as “not secure”
by collinmanderson on Saturday February 10, 2018 @09:55PM
(#16350927)
Right, any software that's hooked up to the internet needs to be updated over time to stay secure, therefore needing to pay for a service or having it go insecure in 2 years.