News for hackers. Stuff that matters.
Re:How not to run a CA by Bombthecat on Thursday March 01, 2018 @12:47PM (#16494292)
The question is: why does cloadflrare even use them?

There are like ten thousand other options...

Re:How not to run a CA by PuffinBlue on Thursday March 01, 2018 @02:29PM (#16495299)
I believe at the time they deployed their Universal SSL, which was over four years ago, is absolutely massive scale, and is free, they were the partner that could actually deliver the necessary integration and infrastructure to handle that sort of load.

Also, they were amongst the only ones to offer ECDSA certificates IIRC.

Cloudflare detailed a little bit about this in this and other blog posts:

https://blog.cloudflare.com/universal-ssl-how-it-scales/

Re:How not to run a CA by prdonahue on Thursday March 01, 2018 @06:24PM (#16497362)
We use several CAs to issue—Comodo, DigiCert, GlobalSign—and will be adding Let's Encrypt once they support i) SHA-2/ECDSA signatures and ii) wildcards.

Having multiple issuers is important for us as each CA, at some point in time, has operational issues. Additionally, as you've seen with Symantec, browsers take action to distrust certain issuers/roots.

When either of these scenarios happens, our customers don't care if it's the third-party that's down—they expect fast and reliable issuance from us (Cloudflare).

Re:How not to run a CA by originalsimba on Thursday March 01, 2018 @07:34PM (#16497775)
If Cloudflare wants wildcards it's so they can have multiple customers, each using completely different origin servers, on a single certificate, which makes those certificates worthless, and I hope Let's Encrypt blacklists Cloudflare from using them when wildcards are launched.
Re:How not to run a CA by waterbomb on Friday March 02, 2018 @03:21AM (#16499945)
They are not worthless. They still protect the data from the user to the Cloudflare servers, and only Cloudflare keeps the private keys for them. Not sure how this would be made any safer by each domain having a separate certificate.

The main issue is that Cloudflare needs to have plain-text traffic to examine, which cannot be done with End-to-End encryption from the client to the origin server, in which case you would definitely need a separate certificate for each domain.

Re:How not to run a CA by duskwuff on Friday March 02, 2018 @01:59AM (#16499674)
What you're describing is a multi-domain certificate, not a wildcard. Let's Encrypt already supports multi-domain certificates.
Re:How not to run a CA by jgrahamc on Friday March 02, 2018 @03:03AM (#16499892)
Huh? We want wildcards so that if you sign up example.com we can give you a certificate for example.com and *.example.com. This has nothing to do with SANs.
Re:How not to run a CA by originalsimba on Sunday March 04, 2018 @05:30AM (#16514120)
However, that is apparently a deal breaker, which makes me suspicious because many organizations have no trouble implementing Let's Encrypt SSL despite the lack of wildcard support. That + Past Behavior = suspicion.
Re:How not to run a CA by jgrahamc on Monday March 05, 2018 @04:35AM (#16519852)
Which part is a deal breaker? I'm not sure what you are getting at.
Re:How not to run a CA by originalsimba on Monday March 05, 2018 @01:11PM (#16522991)
I am quoting an earlier comment in this very thread: "We use several CAs to issue—Comodo, DigiCert, GlobalSign—and will be adding Let's Encrypt once they support i) SHA-2/ECDSA signatures and ii) wildcards."

Did your colleague mis-speak?

Re:How not to run a CA by jgrahamc on Tuesday March 06, 2018 @12:23PM (#16530259)
No
Re:How not to run a CA by niij on Friday March 02, 2018 @01:20AM (#16499527)
How is that misusing a wildcard certificate? Should proxy server websites be HTTP only since the content is loaded from a different origin server?
Re:How not to run a CA by originalsimba on Sunday March 04, 2018 @01:32PM (#16515818)
Why does a proxy server need to decrypt traffic to serve it? Why can't it simply _act as a proxy_?

What Cloudflare does is dangerous to the integrity of safe browsing, for a variety of reasons. And their aggressive marketing to convince a lot of tech-ignorant people with low traffic websites that they need a CDN is harmful.

Is it too much to ask that their service at least operate in a way that doesn't poison the internet they're getting rich from?