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님이 작성:

> 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 
> <https://crt.sh/?q=8ABFC40FAEAF13CBC8BB67B61C8D097A321CD2FEE047C54256927E0F8BFEADFD>
>  
>
> emSign Root Client Auth CA - G3 
> <https://crt.sh/?q=BBD8B3D745EFB79198D93B9C482B9D934537325729EA2F02C129261F91BE2E3D>
>
> emSign Root CS CA - G2 
> <https://crt.sh/?q=0D74EF67C88DE3560365E225AEF976F915E901347B73352D81AB5B4132BB2150>
>  
>
> emSign Root CS CA - G3 
> <https://crt.sh/?q=F2EDAAFF3D9B701FB4D14C9F285F8C0BAD90FC3BCC1FA07D47F4718EDABA34A5>
>  
>
> emSign Root SMIME CA - G1 
> <https://crt.sh/?q=47911BC8F32A11B029E0BB10A348B459404B87731B870A2F3FA97B4705DC4C25>
>  
>
> emSign Root SMIME CA - G3 
> <https://crt.sh/?q=F76A0D440C418DC5B362BE8E11E0A5D06023F4396093E4F455827BF55153D8A4>
>  
>
> emSign Root TLS CA - G1 
> <https://crt.sh/?q=CEF71E70B7C29ADDF6C30CD19E614B38FD5F02A435A0EEDDD0087E183D101A51>
>  
>
> emSign Root TLS CA - G3  
> <https://crt.sh/?q=7DD78D5F4F13459A83DFF9ABBBA62EDBAF6F2D102BF257FD712F4D9F2746ED8D>
>
> emSign Root TSA CA - G2  
> <https://crt.sh/?q=1997770A5633FB6D0440ABF7D7E87E15D795F094F8C2959DADB00E785866BF48>
>
> emSign Root TSA CA - G3 
> <https://crt.sh/?q=75D2CE75979CF2A43B172C9F89F733DDA2136031DB4BBF3698B053714C077155>
>  
>
> This discussion period is scheduled to close on Thursday, September 17, 
> 2026.
>
> Information Supporting this Discussion
>
> Public Incident Reporting History -  [here 
> <https://bugzilla.mozilla.org/buglist.cgi?component=CA%20Certificate%20Compliance%20&product=CA%20Program&short_desc_type=allwordssubstr&query_format=advanced&short_desc=emudhra&resolution=---&resolution=FIXED>
> ]
>
>
> CCADB Root Inclusion Request Cases 1777 
> <https://ccadb.my.salesforce-sites.com/ccadb/CasePrintViewAllPublic?recordId=500TO000006TFHyYAO>,
>  
> 2709 
> <https://ccadb.my.salesforce-sites.com/ccadb/CasePrintViewAllPublic?recordId=500TO00000YV9ZmYAL>,
>  
> and 2898 
> <https://ccadb.my.salesforce-sites.com/ccadb/CasePrintViewAllPublic?recordId=500TO00000fidUKYAY>
> , 
>
> (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
>

-- 
You received this message because you are subscribed to the Google Groups 
"CCADB Public" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion visit 
https://groups.google.com/a/ccadb.org/d/msgid/public/fd68d1af-ceeb-4bd7-9229-0040e7511570n%40ccadb.org.

Reply via email to