News for hackers. Stuff that matters.

A comment on Chrome 68 will mark all HTTP sites as “not secure”. Parent comment

Re:Chrome 68 will mark all HTTP sites as “not secure” by LoSboccacc on Friday February 09, 2018 @02:42AM (#16338593)
Of all the complexity and unknown that are embedded in projects with decades of lifespan, for this one in particular the solution is quite straightforward: roll your own certificate authority and relative certificate distribution and deployment scripts.
[ Parent | on HN ]
Re:Chrome 68 will mark all HTTP sites as “not secure” by merb on Friday February 09, 2018 @02:55AM (#16338643)
This only works when SHA256 certs will be supported for 30 years (which I doubt it won't sustain the next 30 years..)

I know plenty of devices which can't be used correctly any more since SHA1 + SSLv2/SSLv3 was deprecated and they generated a CA+Cert with 512/1024 Bits.

[ Parent | on HN ]
Re:Chrome 68 will mark all HTTP sites as “not secure” by LoSboccacc on Sunday February 11, 2018 @03:44PM (#16354700)
unmaintained unsupervised support is clearly not an issue, which operating system could they chose with that kind of guarantee?
[ Parent | on HN ]