Re:Digicert Withdraws from the CA Security Council
by hoppa_liza on Sunday July 01, 2018 @08:51PM
(#17438615)
Was it confirmed to be GoDaddy? That is dishonest marketing to say the least.
Re:Digicert Withdraws from the CA Security Council
by gpm on Sunday July 01, 2018 @09:29PM
(#17438752)
I assume it was edited in. But to be clear to future readers, the bracketed link in grandparent links to a tweet proving they did.
A more direct link to where they admit it (and publicly try to fix the mistake) is this: https://twitter.com/perezbox/status/1011708133960536064
They don't admit to a general pattern of mistakes like this there, they do say they will use this "as a learning opportunity for all our agents. Whether that is because this was genuinely a one off or because this is the only publicized example is unclear.
CASC member GoDaddy cold-called a random musician with an HTTP site and told her the only way to avoid an SSL warning from Google would be to pay them $200+: https://www.facebook.com/rebecca.ann.925/posts/1740244236062...
I can see why Digicert would want to run from the CASC and keep their reputation safe.
(from Ryan Sleevi of Chrome's crypto team https://twitter.com/sleevi_/status/1012338888088719360 - searching for his other interactions with the CA Security Council is pretty enlightening too)