CAcert.org

CAcert.org is a community-driven certificate authority that issues free public key certificates to the public.[1] As of July 2016, CAcert had over 334,000 verified users and had issued over 1,285,000 certificates.[2] CAcert.org heavily relies on automation and therefore issues only Domain-validated certificates (and not Extended validation or Organization Validation certificates).

CAcert Inc.
Nonprofit organization
IndustryCertificate authority
Founded24 July 2003 (24 July 2003)
FounderDuane Groth
Headquarters
Murwillumbah, New South Wales
,
Area served
World
Websitewww.cacert.org

These certificates can be used to digitally sign and encrypt email, to authenticate and authorize user connections to websites, and to secure transmissions over the Internet. Applications that support (SSL) can use certificates signed by CAcert, as can applications that use X.509 certificates, e.g. to encrypt or to sign code and documents.

CAcert Inc. Association

CAcert Inc. is an incorporated non-profit association registered[3] in New South Wales (Australia) which runs CAcert.org -- a community-driven certificate authority. Its members live in various countries. Its board consists of 7 members.[4] It was founded by Duane Groth in July 2003. In 2004, the Dutch Internet pioneer Teus Hagen became involved. He served as board member and, in 2008, as president.[5]

Certificate Trust status

Since 29 August 2018, most browsers don't automatically trust certificates issued by CAcert. Thus, users receive a "untrusted certificate" warning upon trying to view a website that is signed by CAcert. For email use, MS Outlook doesn't automatically accept these certificates either. CAcert uses its own certificate on its website.

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[6]—verify other users; more assurance points allow the Assurer to assign more assurance points to others.

CAcert sponsors key signing parties, especially at big events such as CeBIT and FOSDEM. CAcert's web of trust has 365,201 verified users as of 2019-02-14.

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.[7]

Inclusion status

The habit to include a list of CAs in the browser was established with Netscape Navigator v.3.0.[8] It was 1996, the dawn of the first browser war, and little emphasis was put on the security implications of making such a list. The key concern was the users' ability to quickly access secured web pages, almost irrespectively of the signing CA.[9] Browsers needed to not skip any important CA included by their competitors.

CAcert arrived much later. Discussion for inclusion of its root certificate in Mozilla and derivatives (such as Mozilla Firefox) started in 2004. Mozilla had no CA certificate policy at the time. Eventually, they developed a policy which required that CAcert improved their management system and deepened their formal verifications, auditing in particular. CAcert withdrew its request for inclusion at the end of April 2007.[10] Progress toward Mozilla requirements and a new request for inclusion can hardly be expected in the near future.[10] At the same time, the CA/Browser Forum was established to allow peaceful discussion among browser producers. Mozilla's advice was adopted, and, in addition, Extended Validation Certificates began to be issued.

FreeBSD included CAcert's root certificate but removed it in 2008, following Mozilla's policy.[11] In 2014, it was removed from Ubuntu,[12] Debian,[13] and OpenBSD.[14] In 2018, it was removed from Arch Linux.[15]

The following operating systems or distributions include the CAcert root certificate, or have it available in an installable package:[16]

gollark: Or at least important features of how fares are encoded mean that this could happen, but in practice it's just quite hard.
gollark: This seems really terrible. Apparently airline pricing is so byzantine that some problems in it are literally uncomputable.
gollark: http://www.demarcken.org/carl/papers//ITA-software-travel-complexity/text0.html
gollark: I can mostly only think of food and water as immediately problematic things, and it's still a lot easier to import help when on the ground.
gollark: Terrestrial housing gets breathable air and some degree of temperature control "for free".

See also

References

  1. "FAQ/AboutUs - CAcert Wiki". wiki.cacert.org. Retrieved September 24, 2019.
  2. "Welcome to CAcert.org". www.cacert.org. Retrieved September 24, 2019.
  3. "CAcertInc - CAcert Wiki". wiki.cacert.org. Retrieved September 24, 2019.
  4. "Brain/CAcertInc/Committee - CAcert Wiki". wiki.cacert.org. Retrieved September 24, 2019.
  5. "NLnet; Teus Hagen". nlnet.nl. Retrieved September 24, 2019.
  6. Assurance Policy, section 2.3.
  7. "FAQ/TechnicalQuestions - CAcert Wiki". wiki.cacert.org. Retrieved September 24, 2019.
  8. Simson Garfinkel; Gene Spafford (2002). Web Security, Privacy & Commerce. O'Reilly Media, Inc. ISBN 9780596000455. Netscape Navigator Version 3.0 came preloaded with certificates for 16 CAs at 11 companies (AT&T, BBN, Canada Post Corporation, CommerceNet, GTE CyberTrust, Keywitness, MCI Mail, RSA, Thawte, U.S. Postal Service, and Verisign.)
  9. "Netscape Navigator 3.0 reviewer's guide". 1996. Archived from the original on 30 December 1996. Retrieved 22 February 2017. Netscape Navigator allows you to connect to server sites whose certificates have been signed by unknown certifying authorities (CAs)
  10. "215243 - CAcert root cert inclusion into browser". bugzilla.mozilla.org. Retrieved September 24, 2019.
  11. 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.
  12. Luke Faraone (5 December 2013). "CAcert should not be trusted by default". Ubuntu Launchpad Bug report logs. Retrieved 14 March 2014.
  13. Jake Edge (March 18, 2014). "Debian and CAcert". LWN.net.
  14. Henderson, Stuart (9 April 2014). "CVS: cvs.openbsd.org: src". openbsd-cvs (Mailing list). Retrieved 8 September 2019 via MARC.
  15. "FS#59690 : [ca-certificates] Reconsider CAcert inclusion". bugs.archlinux.org. Retrieved September 24, 2019.
  16. "CAcert inclusion status page". Archived from the original on 2009-08-26. Retrieved 2007-01-04.
  17. "Debian -- Details of package ca-cacert in sid". Retrieved 1 January 2016.
  18. "Instructions". backports.debian.org. Retrieved September 24, 2019.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.