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. 

-----Original Message-----
From: Kurt Roeckx [mailto:[email protected]] 
Sent: Thursday, March 9, 2017 5:40 PM
To: [email protected]
Cc: Jeremy Rowley <[email protected]>;
[email protected]
Subject: Re: DigiCert BR violation

On Thu, Mar 09, 2017 at 06:29:57PM -0500, Ryan Sleevi via
dev-security-policy wrote:
> > However, I think this discussion raises some very interesting points 
> > about real world scenarios and RFC 5280 that should be addressed.  
> > DigiCert actually has three items that routinely show up on CABLint:
> > 1)      Use of teletext in strings (although this only occurs in
> > re-issues/duplicates of previously issued certificates)
> >
> 
> Is this in the issuer field? Or in the subject information? I can 
> understand if your issuer cert has this issue, but I don't think 
> there's any good reason for this for the subject information.

RFC5280 has this:
4.1.2.6.  Subject
[...]
   When encoding attribute values of type DirectoryString, conforming
   CAs MUST use PrintableString or UTF8String encoding, with the
   following exceptions:
[...]
      (c)  TeletexString, BMPString, and UniversalString are included
           for backward compatibility, and SHOULD NOT be used for
           certificates for new subjects.  However, these types MAY be
           used in certificates where the name was previously
           established, including cases in which a new certificate is
           being issued to an existing subject or a certificate is being
           issued to a new subject where the attributes being encoded
           have been previously established in certificates issued to
           other subjects.  Certificate users SHOULD be prepared to
           receive certificates with these types.

So you could at least argue that TeletexString is allowed in some cases.

But I have never seen a certificate with a properly encoded TeletexString,
except when it only uses characters that are close to what PintableString
allows. Almost all seem to be putting
latin1 charactes in there while G1 is not mapped by default. And even if G1
defaulted to 103, which I've seen some people claim, 103 isn't even close to
latin1, and none of the allowed registration numbers matches latin1 or are
even close. Also note that G0 does not actually map to ASCII by default,
that would be registration 6, while the default for G0 is 102.

As far as I know none of the software I use actually supports decoding
TeletexString. There really isn't any compatibility reason to use
TeletexString. There are only reasons not to use it. And you should have
stopped using it more than 10 years ago.

I would have less of a problem with BMPString or UniversalString, but
TeletexString really just just go.


Kurt

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
dev-security-policy mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-security-policy

Reply via email to