CAcert - Revision history

Kempelen: Category changes: -Openmoko, +Openmoko Inc

2008-09-07T11:29:07Z

Category changes: -Openmoko, +Openmoko Inc

DolfjeBot1: Replacing 'OpenMoko' with 'Openmoko'

2008-08-22T22:44:02Z

Replacing 'OpenMoko' with 'Openmoko'

Glenn: +Category:Openmoko

2008-07-08T06:11:10Z

+Category:Openmoko

Gismo: /* Client Support */

2007-12-05T14:20:07Z

‎Client Support

Gismo: /* Client Support */

2007-12-05T14:19:05Z

‎Client Support

Gismo: /* Openmoko IT Infrastructure */

2007-12-05T14:18:53Z

‎Openmoko IT Infrastructure

Gismo: new page, CAcert basics

2007-12-05T14:18:27Z

new page, CAcert basics

New page

= CAcert and Openmoko =

CACert is utilized and deployed by OpenMoko on multiple systems.

== Openmoko IT Infrastructure ==

On our Infrastructure we deploy [[http://www.cacert.org/ CAcert]] Certificates on all '''SSL''' services.

Many systems have a x509 certificate signed by the CAcert class 3 Root Certificate
'''http://www.cacert.org/index.php?id=3'''

== Client Support ==

So make full use of the CA Certs your client software has to now about the Root Certificate.
Depending on the client you use there will be a popup telling you about security concerns or in worst case will fail entirely.

Integrating the Root Certs to your Application is the best way to archive more reliable encryption.

Applications where you might want to import the root certificates are:

* Webbrowser
* Mailclients
* svn (svn over https/DAV)
* jabber clients
* system wide
** some Linux Distributions supoort /etc/ssl/certs
** on Mac OSX use the Keychain to add Root Certs to X509Anchors

== Common Problems ==

* vhost webserver
** this is a common thread to the whole internet society (http://wiki.cacert.org/wiki/VhostTaskForce)
** we use subjectAltName for multiple FQDNs. checking against this AltName might be broken with some clients.

← Older revision		Revision as of 11:29, 7 September 2008
Line 33:		Line 33:
	** we use subjectAltName for multiple FQDNs. checking against this AltName might be broken with some clients.		** we use subjectAltName for multiple FQDNs. checking against this AltName might be broken with some clients.

−	[[Category:Openmoko]]	+	[[Category:Openmoko Inc]]

← Older revision		Revision as of 06:11, 8 July 2008
Line 32:		Line 32:
	** this is a common thread to the whole internet society (http://wiki.cacert.org/wiki/VhostTaskForce)		** this is a common thread to the whole internet society (http://wiki.cacert.org/wiki/VhostTaskForce)
	** we use subjectAltName for multiple FQDNs. checking against this AltName might be broken with some clients.		** we use subjectAltName for multiple FQDNs. checking against this AltName might be broken with some clients.
		+
		+	[[Category:Openmoko]]

@@ Line 12: / Line 12: @@
 == Client Support ==
-To make full use of the CA Certs your client software has to now about the Root Certificate.
+To make full use of CA Cert your client software has to now about the Root Certificate.
-Depending on the client you use there will be a popup telling you about security concerns or in worst case will fail entirely.
+If this certs are not in place, depending on the client you use there will be a popup telling you about security concerns or in worst case it will fail entirely.
 Integrating the Root Certs to your Application is the best way to archive more reliable encryption.

@@ Line 1: / Line 1: @@
 = CAcert and Openmoko =
-CACert is utilized and deployed by OpenMoko on multiple systems.
+CACert is utilized and deployed by Openmoko on multiple systems.
 == Openmoko IT Infrastructure ==

@@ Line 5: / Line 5: @@
 == Openmoko IT Infrastructure ==
-On our Infrastructure we deploy [[http://www.cacert.org/ CAcert]] Certificates on all '''SSL''' services.
+On our Infrastructure we deploy [http://www.cacert.org/ CAcert] Certificates on all '''SSL''' services.
 Many systems have a x509 certificate signed by the CAcert class 3 Root Certificate