Gervase Markham <[email protected]> wrote: > On 07/12/16 12:44, Brian Smith wrote: >> Notice in the BRs that the KeyUsage extension (not to be confused with the >> ExtendedKeyUsage extension we're talking about here) is optional. Why is it >> OK to be optional? Because the default implementation allows all usages, >> including in particular the usages that browsers need. > > The fact that some defaults are suitable doesn't mean that all defaults > are suitable. You are assuming what you seek to prove.
In your proposal, an end-entity certificate is allowed to have any EKUs in addition to id-kp-serverAuth, right? So, all EKUs are indeed acceptable and so the default is acceptable. > Changing the BRs in this way would (arguably, as the scope of the BRs is > a matter of ongoing debate, something we hope this line of work will > eventually clarify) bring a whole load of certs which are not currently > issued under the BRs and which aren't supposed to be under the BRs, > under the BRs. If a certificate is in scope of the BRs then it must conform to the requirements. In particular, it isn't the case that any certificate that conforms to the requirements is in scope. Therefore, loosening the requirements doesn't change the scope. Cheers, Brian -- https://briansmith.org/ _______________________________________________ dev-security-policy mailing list [email protected] https://lists.mozilla.org/listinfo/dev-security-policy

