No - there are no clients that need Teletext that I'm aware of. ETA on the other issues are the CN field is already fixed to limit the size to 64 characters. For the others, we wanted to talk to the primary customer to let them first know the fix is going live. Should be deployed later this week, but I want to talk to them before committing to a specific date (since all their company names are super long).
-----Original Message----- From: dev-security-policy [mailto:dev-security-policy-bounces+jeremy.rowley=digicert.com@lists.mozilla .org] On Behalf Of Ryan Sleevi via dev-security-policy Sent: Monday, March 13, 2017 3:32 PM To: mozilla-dev-security-pol...@lists.mozilla.org Subject: Re: DigiCert BR violation On Monday, March 13, 2017 at 5:12:39 PM UTC-4, Jeremy Rowley wrote: > I don't disagree that teletext shouldn't be used, and we no longer > include it in new certificate requests or renewals. However, we do > include teletext in certificates that originally had teletext strings but are being re-keyed. > Teletext inclusion wasn't intentional and should shortly be fixed. Are you saying that there are one or more clients that require DigiCert to support Teletext strings? Do you have an ETA on the other issues? _______________________________________________ dev-security-policy mailing list dev-security-policy@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-security-policy
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ dev-security-policy mailing list dev-security-policy@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-security-policy
