Re:StartEncrypt considered harmful today
by sigio on Thursday June 30, 2016 @08:45AM
(#12008101)
Shame that these elemental security issues were present in the first case, and that StartCom went live with such an 'untested' and 'unaudited' product without doing a public-beta like Lets-Encrypt did (with non-trusted-by-default certificates).
[ Parent
| on HN ]
It's also a shame they designed their own protocol instead of just using ACME[1], which is a standards-track IETF draft which has received significant security scrutiny. By ignoring ACME, they even managed to replicate my duplicate signature key selection vulnerability that was fixed in ACME nearly a year ago!
During Let's Encrypt's beta, the certificates were already publicly trusted.
They were untrusted for about a month at least. September 14 - October 19 https://letsencrypt.org/blog/