![Red Hat CERTIFICATE SYSTEM 7.3 - ADMINISTRATION Скачать руководство пользователя страница 144](http://html.mh-extra.com/html/red-hat/certificate-system-7-3-administration/certificate-system-7-3-administration_administration-manual_1427433144.webp)
Chapter 4. Certificate Manager
122
The serial number range allows multiple CAs to be deployed and balances the number of
certificates each CA issues. The combination of an issuer name and a serial number uniquely
identifies a certificate. To ensure that two distinct certificates issued by the same authority do
not contain the same serial number, make sure the serial number ranges do not overlap among
cloned CAs.
When a CA exhausts all its serial numbers, it can be revived it by changing the values in the
Next serial number
and
Ending serial number
fields and restarting the Certificate Manager.
•
Default Signing Algorithm.
Specifies the signing algorithm the Certificate Manager
uses to sign certificates. The options are
MD2withRSA
,
MD5withRSA
,
SHA1withRSA
,
SHA256withRSA
, and
SHA512withRSA
, if the CA's signing key type is RSA.
The signing algorithm specified in the certificate profile configuration overrides the algorithm set
here.
4. Click
Save
.
4.8. Setting Restrictions on CA Certificates through
Certificate Extensions
When a subordinate CA is created, the root CA can generate a CA signing certificate with restrictions
on the types of certificates that the subordinate CA can sign with that signing certificate. These
restrictions are set by setting the constraints in the CA signing certificate profile. The default CA
signing certificate request profile is the caCACert profile. By default, there are no restrictions on the
types of certificates that can be signed. The type restrictions are set through the Basic Constraints or
through the Key Usage or Extended Key Usage extensions.
NOTE
Subordinate CA signing certificates can have constraints for the types of extensions which
they can attach to a certificate. It is possible for a subordinate CA to issue certificates
that violate these constraints, but a client authenticating a certificate that violates those
constraints will not accept that certificate.
All CA certificates should contain the
basicConstraints
extension, as this is the standard way to
identify a CA certificate.
Extensions Present
Description
Only
basicConstraints
The certificate is a CA certificate if the
cA
component is true.
Path length processing is done as described in
Section A.3.3,
“basicConstraints”
.
Only a key usage extension
Either the Key Usage or the Extended Key Usage extension
can be set to indicate that the certificate is a CA certificate
if the extension constraints are set for SSL or S/MIME
certificates.
Neither extension
The certificate is not a CA.
Both extensions
The certificate is a CA certificate if the
cA
component of
basicConstraints
is true. If the constraints for SSL or S/
Содержание CERTIFICATE SYSTEM 7.3 - ADMINISTRATION
Страница 1: ...Red Hat Certificate System 7 3 Administration Guide Publication date May 2007 updated March 25 2010 ...
Страница 15: ...xv Index 525 ...
Страница 16: ...xvi ...
Страница 38: ...Chapter 1 Overview 16 Figure 1 4 Certificate System Architecture ...
Страница 82: ...Chapter 2 Installation and Configuration 60 rpm ev rhpki manage ...
Страница 154: ...132 ...
Страница 194: ...172 ...
Страница 238: ...216 ...
Страница 244: ...222 ...
Страница 246: ...224 ...
Страница 286: ...264 ...
Страница 292: ...270 ...
Страница 318: ...Chapter 13 Certificate Profiles 296 Parameter IssuerType_n IssuerName_n ...
Страница 321: ...Freshest CRL Extension Default 299 Parameter PointName_n PointIssuerName_n ...
Страница 371: ...Configuring Mappers 349 Figure 15 9 Selecting a New Mapper Type 6 Edit the mapper instance and click OK ...
Страница 398: ...376 ...
Страница 412: ...390 ...
Страница 472: ...450 ...
Страница 500: ...Appendix A Certificate and CRL Extensions 478 Parameter namen Table A 8 IssuerAlternativeName Configuration Parameters ...
Страница 506: ...484 ...
Страница 528: ...506 ...
Страница 546: ...524 ...