News for hackers. Stuff that matters.
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).
Re:StartEncrypt considered harmful today by agwa on Thursday June 30, 2016 @11:45AM (#12009336)
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!

[1] https://datatracker.ietf.org/wg/acme/charter/

Re:StartEncrypt considered harmful today by schoen on Thursday June 30, 2016 @01:39PM (#12010274)
During Let's Encrypt's beta, the certificates were already publicly trusted.
Re:StartEncrypt considered harmful today by sp332 on Thursday June 30, 2016 @02:18PM (#12010577)
They were untrusted for about a month at least. September 14 - October 19 https://letsencrypt.org/blog/