Setting a CA to Use a Different Certificate to Sign CRLs
181
6.3.4. Setting a CA to Use a Different Certificate to Sign CRLs
A Certificate Manager uses the key pair corresponding to the CA signing certificate for signing
certificates and certificate revocation lists (CRLs). To use a different key pair to sign the CRLs that
the Certificate Manager generates, then a CRL signing certificate can be created. The Certificate
Manager's CRL signing certificate must be signed or issued by itself.
To enable a Certificate Manager to sign CRLs with a different key pair, do the following:
1. Request and install a CRL signing certificate for the Certificate Manager.
This can be done through the certificate wizard in
System Keys and Certificates
in the console.
Use the wizard to request a certificate of the "other" type, and specify "crlSigning" as the certificate
type.
Alternatively, use the
certutil
tool to generate a key pair, request a certificate for the key pair,
and install the certificate in the Certificate Manager's certificate database. For more information
about the
certutil
tool, see
http://www.mozilla.org/projects/security/pki/nss/tools/
.
2. When the certificate request has been created, submit it through the Certificate Manager end-
entities page. The page has a URL in the following format:
https://
hostname:port
/ca/ee/ca
3. After the request is submitted, log into the agent services page.
4. Check the request for required extensions. The CRL signing certificate must contain the
Key
Usage
extension with the
crlSigning
bit set.
5. Approve the request.
6. After the CRL signing certificate is generated, install the certificate in the Certificate Manager's
database through
System Keys and Certificates
in the console.
7. Stop the Certificate Manager.
8. Update the Certificate Manager's configuration to recognize the new key pair and certificate.
a. Open the Certificate Manager instance configuration directory.
/var/lib/pki-ca/conf
b. Open the
CS.cfg
file.
c. Add the following lines to the configuration file:
ca.crl_signing.cacertnickname=
nickname
cert-
instance_ID
ca.crl_signing.defaultSigningAlgorithm=
signing_algorithm
ca.crl_signing.tokenname=
token_name
nickname
is the name assigned to the CRL signing certificate;
instance_ID
is the name
of the Certificate Manager instance;
signing_algorithm
is
MD5withRSA
,
MD2withRSA
, or
SHA1withRSA
, if the key type is RSA; and
token_name
is the name of the token used
Содержание CERTIFICATE SYSTEM 8.0 - ADMINISTRATION
Страница 1: ...Red Hat Certificate System 8 0 Admin Guide Publication date July 22 2009 updated on March 25 2010 ...
Страница 42: ...20 ...
Страница 43: ...Part I Setting up Certificate Services ...
Страница 44: ......
Страница 190: ...168 ...
Страница 208: ...186 ...
Страница 223: ...Part II Additional Configuration to Manage CA Services ...
Страница 224: ......
Страница 256: ...234 ...
Страница 270: ...248 ...
Страница 280: ...258 ...
Страница 292: ...270 ...
Страница 293: ...Part III Managing the Subsystem Instances ...
Страница 294: ......
Страница 363: ...Managing RA Users 341 5 The user details page shows the person s UID full name email address and user SSL certificate ...
Страница 408: ...386 ...
Страница 438: ...416 ...
Страница 439: ...Part IV References ...
Страница 440: ......
Страница 503: ...Netscape Defined Certificate Extensions Reference 481 OID 2 16 840 1 113730 13 ...
Страница 504: ...482 ...
Страница 556: ...534 ...
Страница 564: ...542 ...