Nukeador:
Eddy Nigg (StartCom Ltd.) escribió:
OK, I understand. This request is fairly new, but I also can't see anywhere at this bug that the representative of this CA submitted and completed all information required to start any evaluation according to http://wiki.mozilla.org/CA:Root_Certificate_Requests
Comments #3 <https://bugzilla.mozilla.org/show_bug.cgi?id=408008#c3> and #4 <https://bugzilla.mozilla.org/show_bug.cgi?id=408008#c4> (translation) are evidences of a representative of the CA asking for inclusion and the attachment <https://bugzilla.mozilla.org/attachment.cgi?id=321673> has the information requested in that wiki page.

Am I missing something?

Apparently yes! From http://wiki.mozilla.org/CA:Root_Certificate_Requests see the lower section. I suggest that the representative of the CA starts a new bug according to the instructions of this page:

CA Details
----------

CA Name:     [                                                     ]

Website URL: [http://                                              ]

CA Summary:
  [ A one Paragraph Summary of your CA,                            ]
  [ including the following:                                       ]
  [ - General nature (e.g., commercial, government,                ]
  [                   academic/research, nonprofit)                ]
  [ - Primary geographical area(s) served                          ]
  [ - Number and type of subordinate CAs                           ]

Audit Type (WebTrust, ETSI etc.):  [                               ]

Auditor:  [                                                        ]

Auditor Website URL: [http://                                      ]

Audit Document URL(s):
  [http://                                                         ]
  [http://                                                         ]

URL of certificate hierarchy diagram (if available):
  [http://                                                         ]

Certificate Details
-------------------
(To be completed once for each root certificate; note that we only
 include root certificates in the store, not intermediates.)

Certificate Name:  [ a short name, 60 characters max, no ':'       ]

Summary Paragraph:
  [ including the following:                                       ]
  [ - End entity certificate issuance policy,                      ]
  [   i.e. what you plan to do with the root                       ]

Root certificate download URL (on CA website):
  [http://                                                         ]
  [alternatively, paste a copy of the certificate in "PEM" format  ]

Certificate SHA1 Fingerprint (in hexadecimal):
  [ XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    ]

Key size (for RSA, modulus length) in bits: [                      ]

Valid From (YYYY-MM-DD): [                                         ]
Valid To (YYYY-MM-DD):   [                                         ]

CRL HTTP URL (if any):
  [http://                                                         ]

CRL issuing frequency for subordinate CA certificates: [      days ]
CRL issuing frequency for subordinate EE certificates: [      days ]

OCSP responder URL (if any):
  [http://                                                         ]

Class: [domain-validated, identity/organizationally-validated or EV ]

Certificate Policy URL:
  [http://                                                         ]

CPS URL:
  [http://                                                         ]

Requested Trust Indicators: [ email and/or SSL and/or code signing ]

URL of a sample website using a certificate chained to this root
(if applying for SSL):
  [https://                                                        ]


_______________________________________________
dev-tech-crypto mailing list
dev-tech-crypto@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-tech-crypto

Reply via email to