Closed Bug 369519 Opened 18 years ago Closed 18 years ago

Add Certipost E-Trust root certificates

Categories

(CA Program :: CA Certificate Root Program, task, P2)

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: bart.callens, Assigned: gerv)

References

Details

User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.1.4322; .NET CLR 2.0.50727) Build Identifier: the certificate data (or links to the data) for the CA certificate(s) requested for inclusion; The 4 (self-signed) CA Certificates that are requested to be included are available for download on following location : http://www.certipost.be/download/Root%20and%20Primary%20CA%20certs.zip for each CA certificate requested for inclusion, whether or not the CA issues certificates for each of the following purposes within the CA hierarchy associated with the CA certificate: SSL-enabled servers, digitally-signed and/or encrypted email, or digitally-signed executable code objects; 1_Root SSL-enabled servers, digitally-signed and/or encrypted email, or digitally-signed executable code objects; 1.1_PrimaryQualifiedCA digitally-signed email 1.2_PrimaryNormalisedCA SSL-enabled servers, digitally-signed and/or encrypted email, or digitally-signed executable code objects; 1.3_PrimaryLightweightCA SSL-enabled servers, digitally-signed and/or encrypted email, or digitally-signed executable code objects; a Certificate Policy and Certification Practice Statement (or links to a CP and CPS) or equivalent disclosure document(s) for the CA or CAs in question; cfr attachment and information as to how the CA has fulfilled the requirements stated above regarding its verification of certificate signing requests and its conformance to a set of acceptable operational criteria. Detail description of this is included in the CPS in attachment. Finally, Certipost E-Trust is controlled by the Belgian Federal Public Service Economy, SMEs, Self-employed and Energy in conformity with the Belgian law of 9 July 2001 and European Directive on Digital Signatures, fixing certain rules related to the legal framework for electronic signatures and certification services. The list of controlled entities is published on http://www.mineco.fgov.be/information_society/e-signatures/list_e_signature_fr.pdf. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Summary: CA Root Certs inclusion → Add Certipost E-Trust root certificates
Status: UNCONFIRMED → NEW
Ever confirmed: true
Priority: -- → P2
Hi Bart, Thanks for reissuing your request and providing that information. Since I contacted you last, I've come up with a comprehensive list of all that we need to know - in order to prevent a lot of back and forth. Could you possibly complete the following? Please give data in the following format, as a *plain text comment*. This will help me do whatever evaluation is necessary, and then will be part of a public record describing the Mozilla default root certificates. CA Details ---------- CA Name: Website: One Paragraph Summary of 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: Audit Document URL(s): Certificate Details ------------------- (To be completed once for each certificate) Certificate Name: Summary Paragraph, including the following: - End entity certificate issuance policy, i.e. what you plan to do with the root Certificate HTTP URL (on CA website): Version: SHA1 Fingerprint: MD5 Fingerprint: Modulus Length (a.k.a. "key length"): Valid From (YYYY-MM-DD): Valid To (YYYY-MM-DD): CRL HTTP URL: OCSP URL: Class (domain-validated, identity-validated or EV): Certificate Policy URL: CPS URL: Requested Trust Indicators (email and/or SSL and/or code): Thanks for your help in this matter. :-) Gerv
Bart: It's been over a month. Are you able to provide the requested information? Thanks, Gerv
Reassign all open CA bugs to me. Apologies for the bugspam. Gerv
Assignee: hecker → gerv
Hardware: PC → All
No response from requester; resolving INCOMPLETE. Please reopen when/if the requested information is available. Gerv
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → INCOMPLETE
Product: mozilla.org → NSS
Product: NSS → CA Program
You need to log in before you can comment on or make changes to this bug.