Comment 193 for bug 232340

(In reply to comment #148)
> If you already know how to obtain and install a root certificate, what is the
> urgency of having it pre-installed in Mozilla products?

Well, that logic would suggest that we not include ANY root certs in the browser, so that every secured website pops up all kinds of alarm bells. Except, by doing that you're going to relegate Mozilla products to irrelevance to the common user.

In the same way, by not including the CACert in the brower, you're relegating their certificates to irrelevance to the common website owner. Would amazon.com want to have Firefox pop up all kinds of bells and whistles when a customer drops by?

It seems strange that Mozilla wouldn't see CACert as a natural partner. In theory both have a goal of creating an open community solution to web standards.

Offering workaround solutions to those tracking this bug isn't very useful - having CACert listed as a trusted root CA doesn't help CACert users who using Mozilla products. It helps website owners who are CACert users who have visitors using Mozilla products. Those visitors have never heard of CACert, just as they've never heard of Verisign/Thawte/etc, and it is very unlikely that they'd be able to implement these sorts of workarounds.