Kathleen, For clarity's sake, it may make sense to update the text to make it clear that this requirement extends to SXG certificates which some may presume are "non-TLS" which I believe would be an invalid interpretation.
I would also be interested to understand if you believe the non-TLS certificate limitation is currently intended to be the first phase of this requirement and similarly if there would be any issue if a CA included more than non-TLS certificates when they implemented this new requirement. Ryan Hurst On Monday, July 19, 2021 at 2:39:54 PM UTC-7 [email protected] wrote: > All, > > The CCADB has been updated as follows: > > - Updated the ‘JSON Array of Partitioned CRLs’ field to increase the > maximum number of characters to 20,000. > - Updated the API > > <https://github.com/mozilla/CCADB-Tools/tree/master/API_AddUpdateIntermediateCert> > > to all for up to 20,000 characters in this field > - Renamed the ‘Pertaining to Certificates Issued by this CA’ section > to ‘Pertaining to Non-TLS Certificates Issued by this CA’. Also updated > the > corresponding help text and the instructions at > www.ccadb.org/cas/fields to indicate that these full CRL fields are > currently intended for the full CRLs pertaining to Non-TLS certificates. > > Thanks, > Kathleen > > > -- You received this message because you are subscribed to the Google Groups "[email protected]" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/mozilla.org/d/msgid/dev-security-policy/057bdd99-cd1d-442f-ad6e-a92afb25da6fn%40mozilla.org.
