Comment 85 for bug 232340

(In reply to comment #84):
Erik, I think you misunderstand the issue at hand. The problem is not that the
Mozilla Foundation is taking too long to include CACert's root certificate into
its products "by default" or the fact that end-users see a security warning when
visiting SSL sites secured by a certificate issued by an "untrusted" CA, such as
CACert.

The problem is that the Mozilla Foundation doesn't really have a solid policy
that governs these situations. Before we discuss CACert (or any other CA, be
they "open/free" or not), the Mozilla Foundation needs to come up with a policy
for reviewing CAs such as CACert.

One thing I'll hand to you, though: this issue has dragged on long enough. A
decision should be made relatively soon for the good of everyone involved.

P.S. Discussions of these sorts should really be held at the forums (usenet/web
forums).