Re:Chrome 68 will mark all HTTP sites as “not secure”
by tokenizerrr on Thursday February 08, 2018 @03:48PM
(#16335458)
Unless I'm misunderstanding they did that by partnering with a CA. Becoming a semi-trusted CA themselves. This is not an option for most organizations.
[ Parent
| on HN ]
Re:Chrome 68 will mark all HTTP sites as “not secure”
by Ajedi32 on Thursday February 08, 2018 @04:04PM
(#16335590)
That was only necessary because, at the time, there was no other way to get a large number of wildcard certs issued for their domain in an automated fashion.
With ACME that will no longer be the case. Let's Encrypt will allow you to do basically the same thing for free with ~20 devices a week[1] starting on February 27[2], for example. In the future, commercial CAs may choose to offer similar services with more relaxed rate limits.
[1]: https://letsencrypt.org/docs/rate-limits/
[2]: https://letsencrypt.org/2017/07/06/wildcard-certificates-com...
Re:Chrome 68 will mark all HTTP sites as “not secure”
by tokenizerrr on Thursday February 08, 2018 @04:40PM
(#16335820)
Yeah, would be nice if ACME with DNS validation was widespread. But right now it's still not viable due to Let's Encrypt's rate limits.
Re:Chrome 68 will mark all HTTP sites as “not secure”
by pfg on Thursday February 08, 2018 @04:44PM
(#16335854)
It's fairly trivial to request a rate limit adjustment from Let's Encrypt[1].
[1]: https://docs.google.com/forms/d/e/1FAIpQLSetFLqcyPrnnrom2Kw8...