3,250
edits
Changes
Jump to navigation
Jump to search
Line 2:
Line 2: + + Line 90:
Line 92: + + Line 104:
Line 108: − + − +
Custom CA Certificate (view source)
Revision as of 03:34, 23 September 2009
, 03:34, 23 September 2009no edit summary
Author: slords
Author: slords
updated: unnilennium (http://bugs.contribs.org/show_bug.cgi?id=1370)
== creating .csr and .key files ==
As root do the following:
As root do the following:
From here replace the <b>{domain}</b> tag with your Primary domain name. Also you will need to have all domains registered with your cacert.org account. This will create a certificate that includes all domains that exists on your sme box as both simple domain.com and wildcard *.domain.com.
From here replace the <b>{domain}</b> tag with your Primary domain name. Also you will need to have all domains registered with your cacert.org account. This will create a certificate that includes all domains that exists on your sme box as both simple domain.com and wildcard *.domain.com.
== obtain .crt file from cacert==
*Paste the output into the cacert.org website and get your certificate
*Paste the output into the cacert.org website and get your certificate
cat {domain}.csr
cat {domain}.csr
== configuring your sme with your new certificate==
Then save your CA certificate in a file named ~/cacert/{domain}.crt
Then save your CA certificate in a file named ~/cacert/{domain}.crt
*and apply the changes
*and apply the changes
signal-event console-save
signal-event post-upgrade
reboot
signal-event reboot
Once you have created/installed this certificate then if the client has the cacert.org root certificate installed then they should be able to go to any domain on your box and not get a warning.
Once you have created/installed this certificate then if the client has the cacert.org root certificate installed then they should be able to go to any domain on your box and not get a warning.