4 ms·
There's one thing that gives me pause here: The single most common error is listed as DNS/URI/email format violations. There is absolutely no discussion as to
by jcranmer 8y ago
There's one thing that gives me pause here:
The single most common error is listed as DNS/URI/email format violations. There is absolutely no discussion as to what kinds of violations these break into, nor is there even a discussion as to what the paper thinks the correct formats ought to be. This is unfortunate because the format of these parameters is one thing where specifications often have a view of the world which is completely incongruent with reality. As a simple case, you will sometimes come across documentation that thinks that DNS names cannot start with a digit, which does not match reality at all.
- tialaramex 8y agoIf they don't discuss it, it seems reasonable to assume they mean as specified. PKIX and the Baseline Requirements are pretty clear on how this works, despite ignorance from the CAs and end users. Note in particular that SAN dnsNames in PKIX are host names, and not all DNS names are acceptable names for hosts per the specifications. In my experience "I wasn't sure of the format definition" is code for "I knew this was strictly forbidden but it's more convenient for me this way, now I can claim to be outraged when it's pointed out and demand extra time to correct it". This works up to a point, but these things pile up. One small mistake is very forgiveable, except in the context of having made lots of other (perhaps convenient for you) "mistakes" and then it looks like incompetence regardless of your actual motivation.
- C1sc0cat 8y agogrin I have seen this working with x.400 mail - Sprint flat out ignored stuff. ICL decided to start an index at 0 when the spec said MUST start at 1 - and oops look a divide by zero error
- bluejekyll 8y ago> As a simple case, you will sometimes come across documentation that thinks that DNS names cannot start with a digit, which does not match reality at all. I wish that were true. It’s seriously annoying that DNS names are nearly indistinguishable from ipv4 addresses.
- technion 8y agoTo complicate this further, there are certificates issued with IP addresses as names. One of the early bugs in CT Advisor[0] involved not knowing what to do with such a thing. I'd be interested in whether those writing this report considered these a valid URI. An obvious example: https://1.1.1.1/ https://1.1.1.1/ [0] https://ctadvisor.lolware.net/ https://ctadvisor.lolware.net/
- tialaramex 8y agoOlder versions of Microsoft Windows don't understand the ipAddress SAN at all. Instead they parse the dnsName SANs as a generic text field into which you can write host names, IP addresses, or whatever you like. This was fixed in modern Windows (maybe Windows 7 onwards?) As a result, and with enforcement never total, CAs would often issue non-compliant garbage for IP addresses because "it works on Windows". In the last few years this has improved as older Windows systems rust out and enforcement becomes more proactive. 1.1.1.1 is an example of how this should look.
- deleted 8y ago[deleted]
- XMPPwocky 8y agoI'm seeing the SAN for the cert served by 1.1.1.1 to contain the IP 1.1.1.1, not the domain 1.1.1.1. Or am I misunderstanding?
- technion 8y agoYes, the name is listed in the SAN on that cert. That said, that's one of the fields that's parsed, and potentially a source of issues in this paper.
- cryptonick 8y agoI am the main author of the paper, I am glad to see such an interesting discussion aroused on our work. In general, to address the concerns about the validation of the information found in the certificate, I remark that we targeted only syntactic checking: that is, we just verify that the format of the IP address or the DNS names is compliant to the X.509 specifications. Instead, the validation of the information retrieved by the parsing can be done by an application built on top of our parser. Therefore, a URI/DNS/IP address is valid if it is compliant to the syntactic format described in the standard. Regarding the specific example, I run our parser on that certificate: since the IP addresses in SAN have the correct format, they are correctly recognized. This certificate provides an example of a bad DNS name: indeed, it contains a DNS name starting with *. Although I could expect that this might sounds reasonable, such a Domain Name is not allowed by X.509 specification.