Re: Gen-ART review of draft-ietf-jose-json-web-signature-33

[John Bradley <ve7jtb@xxxxxxxxxx>]

The attack is not possible if the receiver validates the host from the x5u against the certificate CN and validates the path,  otherwise any valid certificate would work, as long as it chains to a valid root.

Yes we could explain that that the client could limit itself to a specific root or bridge and use the CN or DN for the identity of the signer.  

So yes it is possible to make an exception to the MUST but explaining how to do that safely is not trivial, and may cause more harm than good.

John B.

On Sep 30, 2014, at 4:53 PM, Dave Cridland <dave@xxxxxxxxxxxx> wrote:

On 30 September 2014 20:37, John Bradley <ve7jtb@xxxxxxxxxx> wrote:

I agree, the likelihood of the application correctly walking the path and validating the chain is very small.  

I think the likelihood of the application being *able* to is small given the scope - however if it can, we should assume that it will.

 

I strongly prefer leaving it a MUST use TLS and validate the server per RFC 6125.

The other thing to note is that the CN of the cert is not in the header.  If TLS is not used an attacker could simply modify the DNS to retrieve any valid certificate and use that to sign.

Whilst I agree there's a range of attacks possible against non-validating clients - although "the CN of the cert" sets my teeth on edge - an attacker cannot do these if the application performs path validation and checks the key matches.

"SHOULD" and "MUST" are not a stick to beat the unthinking implementer, and if there exist perfectly reasonable cases where this particular MUST can be ignored, then by insisting on a MUST here we are simply weakening the emphasis that all other RFC 2119 language has in this document.

"MUST unless you do X" is a compromise I'd be happy with, although that is basically what "SHOULD" means.

Certainly this does require the rationale be documented in any case.

Dave.

<<attachment: smime.p7s>>