|This article relies on references to primary sources. (April 2012)|
CAcert.org is a community-driven certificate authority that issues free public key certificates to the public. CAcert has over 260,000 verified users and has issued over 1,000,000 certificates as of January 2014[update].
These certificates can be used to digitally sign and encrypt email, authenticate and authorize users connecting to websites and secure data transmission over the Internet. Any application that supports the Secure Socket Layer (SSL) can make use of certificates signed by CAcert, as can any application that uses X.509 certificates, e.g. for encryption or code signing and document signatures.
CAcert Inc. Association
CAcert Inc. is an incorporated non-profit association registered in New South Wales (Australia) since July 2003 which runs CAcert.org. It has members living in many different countries and a board of 7 members.
CAcert automatically signs certificates for email addresses controlled by the requester and for domains for which certain addresses (such as "firstname.lastname@example.org") are controlled by the requester. Thus it operates as a robot certificate authority. These certificates are considered weak because CAcert does not emit any information in the certificates other than the domain name or email address (the CommonName field in X.509 certificates).
Web of trust
To create higher-trust certificates, users can participate in a web of trust system whereby users physically meet and verify each other's identities. CAcert maintains the number of assurance points for each account. Assurance points can be gained through various means, primarily by having one's identity physically verified by users classified as "Assurers".
Having more assurance points allows users more privileges such as writing a name in the certificate and longer expiration times on certificates. A user with at least 100 assurance points is a Prospective Assurer, and may—after passing an Assurer Challenge—verify other users; more assurance points allow the Assurer to assign more assurance points to others.
Root Certificate descriptions
Since October 2005, cacert offers Class 1 and Class 3 root certificates. Class 3 is a high-security subset of Class 1.
As of May 2013[update], certificates issued by CAcert are not as useful in web browsers as certificates issued by commercial CAs such as VeriSign, because most installed web browsers do not distribute CAcert's root certificate. Thus, for most web users, a certificate signed by CAcert behaves like a self-signed certificate. Discussion for inclusion of CAcert's root certificate in Mozilla and derivatives (such as Mozilla Firefox) started in 2004, when Mozilla had no CA certificate policy. Eventually, Mozilla developed that policy and CAcert withdrew its request for inclusion at the end of April 2007. At the same time, the CA/Browser Forum was established and Extended Validation Certificates began to be issued. CAcert would need to improve their management system and deepen their formal verifications, auditing in particular. Progress toward this and a new request for inclusion can hardly be expected in the near future. FreeBSD, who used to include the root certificate, removed it in 2008, following whatever Mozilla policy. In 2013, a similar request was made to remove CAcert from Debian as well.
The following operating systems or distributions include the CAcert root certificate:
- Arch Linux
- Maemo (installed on Nokia Internet Tablets) (not on Nokia N900)
- Mandriva Linux
- MirOS BSD
- Ubuntu, Xubuntu, Kubuntu, Lubuntu (Not in CAcert inclusion list, but actually provided by package ca-certificates now.)
- Kali Linux (successor to BackTrack 5 linux security distribution)
- About CAcert
- CAcert usage statistics
- CAcertInc - CAcert Wiki
- CAcert Inc. Board of Directors
- Assurance Policy, section 2.3.
- FAQ/TechnicalQuestions - CAcert Wiki
- CAcert inclusion status page
- Discussion by Mozilla on including CAcert root certificate
- CAcert audit comment on Mozilla
- FreeBSD Security Officer (29 June 2008). "ca-roots". FreshPorts. Retrieved 16 December 2013. "The ca_root_ns port basically makes no guarantees other than that the certificates comes from the Mozilla project."
- Ansgar Burchardt (31 July 2013). "ca-certificates: should CAcert.org be included?". Debian Bug report logs. Retrieved 15 December 2013.