On Monday, 27 February 2017 00:53:46 UTC, Itzhak Daniel wrote: > How those lines are parsed? what happens when a client reaches a whitespace? > Will this allow 'vietnamairlines.com' to use 'owa', 'mail' and 'autodiscover' > in their internal infrastructure?
Because they're dnsNames a correctly implemented TLS client needn't "parse" them further at all, either they are an exact case-insensitive match for the server's DNS name or they aren't. On the other hand apparently we can't even rely on a CA to get this right, so who knows if any clients get it wrong. The naming on this certificate suggests it was requested for use with Microsoft's Exchange product, so assuming Microsoft's Internet Explorer / Edge web browser, and their Outlook mail client get this right the certificate was probably simply useless as issued. It /is/ interesting that the subscriber had a previous certificate for the valid set of names, and today the https://owa.vietnamairlines.com/ server (OWA stands for "Outlook Web Access" ie it's a web UI for the mail service) is serving a wildcard from someone else, so perhaps the subscriber concluded GlobalSign were hopeless and stopped using them? I hope they got their money back. _______________________________________________ dev-security-policy mailing list [email protected] https://lists.mozilla.org/listinfo/dev-security-policy

