4 ms·

So *.?

• x3n0ph3n3 6y ago
  Did you bother reading? . doesn't work with subdomains. You need more 's and .'s
  • pedrocx486 6y ago
    Doesn't the title here literally say that it works with subdomains? Or I'm misunderstanding? (Not my field of work.)
    • cpach 6y ago
      Yes it does, due to the way that it’s structured. AFAICT, the wildcard symbol (asterisk) will not match across the separator (i.e. the period). So ¤.¤ will only match example.com or contoso.com etc, not blog.example.com or sales.contoso.com. If you look at the cert, it has lots of line that looks like this: DNS:¤.¤.¤.¤.¤.¤.¤.¤.¤.¤, DNS:¤.¤.¤.¤.¤.¤.¤.¤.¤.¤.¤, In that way it will match all possible levels of subdomains. (Asterisk substituted for ¤ in order to not trip up the formatting here on HN.)
  • cpach 6y ago
    If anyone finds 'x3n0ph3n3’s comment to look weird, it’s because HN ate the asterisks in there.
• infogulch 6y ago
  Look at the certificate details: https://github.com/flotwig/the-one-cert/blob/master/openssl.cnf https://github.com/flotwig/the-one-cert/blob/master/openssl.... You have to have a separate alt name specified for every possible number of subdomains. * does *not* match *.*, or *.*.*, etc
• cpach 6y ago
  I don’t think that ? is a valid operator in this context.