Apple 10.6 Server User Manual


 
Chapter 4 Enhancing Security 69
7 Click the Import button.
If prompted, enter the private key passphrase.
Managing Certicates
After you create and sign a certicate, you won’t do much more with it. Since
certicates cannot be edited, you can either delete, replace, or revoke certicates after
they are created. You cannot change certicates after a CA signs them.
If the information a certicate possesses (such as contact information) is no longer
accurate, or if you believe the private key is compromised, delete the certicate.
If you have previously generated certicates for SSL, you can import them for use by
services. The OpenSSL keys and certicates must be in PEM format.
If you chose custom locations for your SSL certicates with Leopard Server, you must
import them into Certicate Manager if you want them to be available for services.
Custom lesystem locations for certicates cannot be managed for services using
Server Admin for Mac OS X Server v10.6. To use custom le locations, you must edit the
conguration les directly.
When certicates and keys are imported via Certicate Manager, they are put in the
/etc/certicates/ directory. The directory contains four PEM formatted les for every
identity:
The certicate Â
The public key Â
The trust chain Â
The concatenated version of the certicate plus the trust chain (for use with some Â
services)
Each le has the following naming convention:
<common name>.<SHA1 hash of the certicate>.<cert | chain | concat | key>.pem
For example, the certicate for a web server at example.com might look like this:
www.example.com.C42504D03B3D70F551A3C982CFA315595831A2E3.cert.pem
After they are imported, Certicate Manager encrypts the les with a random
passphrase. It puts the passphrase in the System keychain, and puts the resulting PEM
les in /etc/certicates/.
Editing a Certicate
After you add a certicate signature, you can’t edit the certicate. You must replace it
with one generated from the same private key.