Public Discussion of eMudhra Root Inclusion Requests

149 views
Skip to first unread message

Ben Wilson

unread,
Aug 6, 2026, 1:53:59 PM (10 days ago) Aug 6
to public
Greetings,

Purpose of this Public Discussion


The purpose of the public discussion process is to promote openness and transparency by providing an opportunity for public review and comment. Each Root Store Operator conducts its own independent evaluation under its own policies, inclusion criteria, and timelines. Completion of this public discussion does not guarantee any favorable action by any Root Store Operator.


This email commences a six-week public discussion of requests by eMudhra Technologies Limited to include the following certificates as publicly trusted root certificates in one or more Common CA Database (“CCADB”) Root Store Operator’s program: 


emSign Root Client Auth CA - G1 

emSign Root Client Auth CA - G3

emSign Root CS CA - G2 

emSign Root CS CA - G3 

emSign Root SMIME CA - G1 

emSign Root SMIME CA - G3 

emSign Root TLS CA - G1 

emSign Root TLS CA - G3 

emSign Root TSA CA - G2 

emSign Root TSA CA - G3 


This discussion period is scheduled to close on Thursday, September 17, 2026.


Information Supporting this Discussion


Public Incident Reporting History -  [here]


CCADB Root Inclusion Request Cases 1777, 2709, and 2898

(current versions of CCADB output are attached as PDF(s) to this email)

This public discussion announcement provides a snapshot of the data and information available in the CCADB related to these inclusion requests as of the date this public discussion period begins. The attached PDFs reflect the CCADB records as they existed when the PDFs were generated and serve as a baseline record for this discussion. CCADB records are operational in nature and may be updated over time. As a result, the current CCADB data may differ from the attached PDFs. Such differences do not necessarily indicate an error in the discussion record or a post-hoc modification of an inclusion request; rather, they may simply reflect the ongoing maintenance of the CCADB. Participants are encouraged to reference the attached PDFs when evaluating the information available at the outset of this discussion and to consult the live CCADB reports, linked above, for the most current operational data.

Interpretation of the Public Record

Neither the information presented here nor any ensuing public discussions, comments, or observations should be interpreted as a complete or authoritative account of any Root Store Operator's evaluation. Root Store Operators may consider additional factors, inputs, and risk assessments that are not reflected in the public record. The public record is intended to inform consideration, not to constrain, predetermine, or fully explain any Root Store Operator's final decision. Accordingly, conclusions drawn solely from the public record may be incomplete and should not be treated as definitive explanations for any Root Store Operator's decision.

Public Participation

Anyone with concerns or questions specific to these root inclusion requests is encouraged to raise them on the CCADB Public mailing list by replying directly to this discussion thread. Likewise, representatives of the applicant are expected to respond promptly, within the discussion thread, to all questions that are raised.

Thanks,

Ben Wilson
on behalf of CCADB
CCADB Case 2709.pdf
CCADB Case 2898.pdf
CCADB Case 1777.pdf

Suchan Seo

unread,
Aug 10, 2026, 9:26:21 AM (7 days ago) Aug 10
to CCADB Public, Ben Wilson
what would be trust flag each root certs have if they are accepted? don't think mozilla root program have clientauth/code signing/timestamp authority root certificates
2026년 8월 7일 금요일 오전 2시 53분 59초 UTC+9에 Ben Wilson님이 작성:

Ben Wilson

unread,
Aug 10, 2026, 9:46:03 AM (7 days ago) Aug 10
to Suchan Seo, CCADB Public
Greetings,
If you're asking specifically about the Mozilla root program, only the two SMIME and two TLS roots are being considered.
Thanks,
Ben
Reply all
Reply to author
Forward
0 new messages