On 2017-03-09 05:21, Ryan Sleevi wrote:
Well, you still said the same thing, and I understood what you said, but
not why you said it or why you believe it. That's why I was asking for new
details.
Certificate Policy OIDs don't say who the certificate belongs to or who
issued the certificate. They describe the policies relative to how the
certificate was issued and validated. This is much clearer if you read the
relevant ETSI TS/EN series of docs related to Certificate Policies.
To your point about identifying the issuer, I may be misunderstanding your
point, but it sounds like you're just confused about how browsers work.
Browsers don't look up the EV OID to determine who the issuer is, so if
you're concerned that would present a problem, it doesn't.
Instead, browsers look for *any* EV enabled OID in the leaf certificate,
then attempt to build/verify that a chain can be built to one or more root
certificates "enabled" for that OID. If they can, the leaf is called EV,
and the browser determines who issued it by looking at the root.
I would also like to see that all EV certificates actually have the CABF
EV OID, possibly in addition to any CA specific OID. I would actually
like to see that for all CABF OIDs, it's currently only required for the
IV certificates as far as I know.
Kurt
_______________________________________________
dev-security-policy mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-security-policy