18.11.2012 Views

Raytheon Company Public Key Infrastructure (PKI) Certificate Policy

Raytheon Company Public Key Infrastructure (PKI) Certificate Policy

Raytheon Company Public Key Infrastructure (PKI) Certificate Policy

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

10.4 High Assurance Subscriber Signature <strong>Certificate</strong><br />

Note: These certificates are only issued to Trusted <strong>PKI</strong> Operators.<br />

Field Value<br />

Version V3<br />

Serial Number Must be unique<br />

Issuer Signature Algorithm sha-1WithRSAEncryption {1 2 840 113549 1 1 5} or<br />

sha256 WithRSAEncryption {1 2 840 113549 1 1 11}<br />

Issuer Distinguished Name ou=<strong>Raytheon</strong>Root, o=CAs, dc=raytheon, dc=com<br />

Validity Period No longer than 3 years from date of issue expressed in UTC Time until<br />

2049<br />

Subject Distinguished Name Unique X.500 subject DN within the namespace dc=raytheon, dc=com as<br />

specified in Section 7.1.4 of the <strong>Raytheon</strong> CP<br />

Subject <strong>Public</strong> <strong>Key</strong> Information 2048 bit RSA key modulus, rsaEncryption {1 2 840 113549 1 1 1}<br />

Issuer’s Signature sha-1WithRSAEncryption {1 2 840 113549 1 1 5} or<br />

sha256 WithRSAEncryption {1 2 840 113549 1 1 11}<br />

Extension Value<br />

<strong>Key</strong> Usage c=yes; digitalSignature,nonRepudiation<br />

Private <strong>Key</strong> Usage Period c=no; 2 years for 2048 bit keys<br />

Subject Alternative Name c=no; RFC822 email address (required); others optional<br />

Subject Directory Attributes c=no; Entrust User Role= integer, where integer is a numeric role<br />

identifier<br />

CRL Distribution Points 12 c=no<br />

Authority <strong>Key</strong> Identifier c=no; Octet String (same as subject key identifier in the Issuing CA<br />

certificate)<br />

Subject <strong>Key</strong> Identifier c=no; Octet String (same as in PKCS#10 request or calculated by the<br />

Signing CA per RFC 3280 method 1 or other method)<br />

<strong>Certificate</strong> Policies c=no;<br />

SHA-1: {1.3.6.1.4.1.1569.10.1.1} or<br />

SHA-256: {1.3.6.1.4.1.1569.10.1.11}<br />

Authority Information Access c=no; id-ad-caIssuers access method entry contains HTTP URL for .p7c<br />

file containing certificates issued to Issuing CA or LDAP URL pointer to<br />

the ca<strong>Certificate</strong> attribute of the Issuing CA; id-ad-ocsp access method<br />

entry contains HTTP URL for the Issuing CA OCSP Responder<br />

Entrust Version Info c=no; Entrust Authority Security Manager = 7.1; <strong>Key</strong> Update Allowed =<br />

Yes; <strong>Certificate</strong> Category = Enterprise<br />

12 The CRL distribution point extension shall only populate the distributionPoint field. The<br />

distributionPoint field shall contain HTTP (i.e., of the form http://…) URI. The distributionPoint<br />

field may contain LDAP (i.e., of the form ldap://…) URI. The reasons and cRLIssuer fields shall<br />

not be populated. The CRL shall point to a full and complete CRL or a Distribution Point based<br />

partitioned CRL. The Distribution Point field shall contain a full name (i.e, the Distribution Point<br />

field shall not contain nameRelativetoCRLIssuer).<br />

90 7/25/2011

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!