CA:Root Certificate Requests: Difference between revisions

Fill in much more of the bug form for the CA
m (Fix numbered list)
(Fill in much more of the bug form for the CA)
Line 1: Line 1:
If you are an official representative of a Certificate Authority and you wish to apply to have your CA's root certificate(s) included in Mozilla  
If you are an official representative of a Certificate Authority and you wish to apply to have your CA's root certificate(s) included in Mozilla  
products, you should do these steps:
products, you should do the steps shown below.
 
== Essential Steps ==


<ol>
<ol>
<li> Read through [http://www.mozilla.org/projects/security/certs/policy Mozilla CA certificate policy] to determine if your CA is eligible and to learn all the requirements for the certificate to be included in Mozilla products.</li>
<li> Read through [http://www.mozilla.org/projects/security/certs/policy Mozilla CA certificate policy] to determine if your CA is eligible and to learn all the requirements for the certificate to be included in Mozilla products.</li>
<li> If you don't already have an account with [https://bugzilla.mozilla.org Mozilla's bug and enhancement request tracking system bugzilla.mozilla.org], then [https://bugzilla.mozilla.org/createaccount.cgi register for an account]. </li>
<li> If you don't already have an account with [https://bugzilla.mozilla.org Mozilla's bug and enhancement request tracking system bugzilla.mozilla.org], then [https://bugzilla.mozilla.org/createaccount.cgi register for an account]. </li>
<li> [https://bugzilla.mozilla.org/enter_bug.cgi?product=mozilla.org&component=CA%20Certificates Submit an Enhancement request bug] in the bug tracking system, requesting that your CA's root certs be added to Mozilla products.   
<li> Begin creating an enhancement request bug in the bug tracking system,  either by clicking [https://bugzilla.mozilla.org/enter_bug.cgi?alias=&assigned_to=hecker%40hecker.org&blocked=&bug_file_loc=&bug_severity=enhancement&bug_status=NEW&comment=CA%20Details%0D%0A----------%0D%0A%0D%0ACA%20Name%3A%0D%0AWebsite%3A%0D%0AOne%20Paragraph%20Summary%20of%20CA%2C%20including%20the%20following%3A%0D%0A%20-%20General%20nature%20%28e.g.%2C%20commercial%2C%20government%2C%0D%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20academic%2Fresearch%2C%20nonprofit%29%0D%0A%20-%20Primary%20geographical%20area%28s%29%20served%0D%0A%20-%20Number%20and%20type%20of%20subordinate%20CAs%0D%0AAudit%20Type%20%28WebTrust%2C%20ETSI%20etc.%29%3A%0D%0AAuditor%3A%0D%0AAuditor%20Website%3A%0D%0AAudit%20Document%20URL%28s%29%3A%0D%0AURL%20of%20certificate%20hierarchy%20diagram%3A%0D%0A%0D%0ACertificate%20Details%0D%0A-------------------%0D%0A%28To%20be%20completed%20once%20for%20each%20certificate%3B%20note%20that%20we%20only%20include%20root%0D%0Acertificates%20in%20the%20store%2C%20not%20intermediates.%29%0D%0A%0D%0ACertificate%20Name%3A%0D%0ASummary%20Paragraph%2C%20including%20the%20following%3A%0D%0A%20-%20End%20entity%20certificate%20issuance%20policy%2C%0D%0A%20%20i.e.%20what%20you%20plan%20to%20do%20with%20the%20root%0D%0ACertificate%20download%20URL%20%28on%20CA%20website%29%3A%0D%0AVersion%3A%0D%0ASHA1%20Fingerprint%3A%0D%0APublic%20key%20length%20%28for%20RSA%2C%20modulus%20length%29%20in%20bits%3A%0D%0AValid%20From%20%28YYYY-MM-DD%29%3A%0D%0AValid%20To%20%20%20%28YYYY-MM-DD%29%3A%0D%0ACRL%20HTTP%20URL%3A%0D%0ACRL%20issuing%20frequency%20for%20subordinate%20end-entity%20certificates%3A%0D%0ACRL%20issuing%20frequency%20for%20subordinate%20CA%20certificates%3A%0D%0AOCSP%20URL%3A%0D%0AClass%20%28domain-validated%2C%20identity%2Forganizationally-validated%20or%20EV%29%3A%0D%0ACertificate%20Policy%20URL%3A%0D%0ACPS%20URL%3A%0D%0ARequested%20Trust%20Indicators%20%28email%20and%2For%20SSL%20and%2For%20code%20signing%29%3A%0D%0AURL%20of%20example%20website%20using%20certificate%20subordinate%20to%20this%20root%20%0D%0A%28if%20applying%20for%20SSL%29%3A%0D%0A&component=CA%20Certificates&contenttypeentry=&contenttypemethod=autodetect&contenttypeselection=text%2Fplain&data=&dependson=&description=&flag_type-335=X&flag_type-378=X&flag_type-390=X&flag_type-4=X&flag_type-7=X&form_name=enter_bug&keywords=&maketemplate=Remember%20values%20as%20bookmarkable%20template&op_sys=All&priority=--&product=mozilla.org&qa_contact=ca-certificates%40mozilla-org.bugs&rep_platform=All&short_desc=add%20%28Your%20CA%20Name%29%20root%20CA%20certificate&target_milestone=---&version=other this link]
or by following the steps shown below (see Manual bug entry).
Fill in the bug form's template with your CA's details. There is one section requesting information about the CA itself, and one section that should be repeated for each of the Root CA certificates that you wish to have included in Mozilla products. Feel free to expand any answer area as needed. </li>
<li> Submit your enhancement request and note the bug number. </li>
<li> Watch your email mailbox for email from bugzilla-daemon@mozilla.org containing additional requests for information. </li> </ol>
 
== Manual bug entry ==
 
Alternatively, you can click [https://bugzilla.mozilla.org/enter_bug.cgi?product=mozilla.org&component=CA%20Certificates this link] to being creating an enhancement request bug in the bug tracking system, requesting that your CA's root certs be added to Mozilla products.   


The form for the Enhancement request should be filled out with these values:
The form for the Enhancement request should be filled out with these values:
Line 95: Line 105:
(if applying for SSL):
(if applying for SSL):
   [https://                                                        ]
   [https://                                                        ]
</pre></li>
</pre>
<li> Submit your enhancement request and note the bug number. </li>
<li> Watch your email mailbox for email from bugzilla-daemon@mozilla.org containing additional requests for information. </li> </ol>
106

edits