2 ms·
Mis-issuance is creating a certificate that is totally reasonable to create, just with the wrong validation. If you have a human step that lets you override the
by geofft 10y ago
Mis-issuance is creating a certificate that is totally reasonable to create, just with the wrong validation. If you have a human step that lets you override the validation check, or if you get the validation logic wrong (e.g. WoSign/StartCom's thing where they allowed high-numbered ports), etc., you end up with a certificate that is otherwise reasonable for you to have created. And there's a lot of code that goes into validation. But there is never any reasonable use for a backdated certificate, and it's a very simple thing to double-check that your code does right.
If you give CAs a pile of requirements and say "Do not do these incorrectly" (which is what browsers do to all CAs), they can always argue that they made an honest mistake and they fixed it. Maybe they shouldn't have that room for argument, but they do. But if you say "Do not backdate certs," you've given them one thing to get right, that is hard to get wrong by mistake. At that point, a backdated cert implies either malice or losing control of the raw private key material, both of which clearly demand revocation.
- brians 10y agoI know a couple reasons for a backdated cert. Here's one that is easy to explain: backdated clients + emergencies. At least one in a million client devices is backdated by more than three days. It is therefore prudent to wait until a week or more past NotBefore before deploying a cert. If you need a new certificate in a terrible rush, you can backdate. Now, that's not what happened here. I would chalk this up to a cultural shift between the Americans and Europeans making the rules at the CA/B forum and the WoSign folks who honestly never imagined they would be expected to comply with rules that couldn't be checked---that a rule would say "don't sign sha-1 after Jan 1" as opposed to "don't sign sha-1 with a NotBefore after Jan 1."
- dylz 10y agoThey never imagined they would be expected to comply with rules they explicitly agreed to?
- geofft 10y agoHm, that's a fair reason. But really what's important here is the fixed CT cutoff date. If you have mandatory CT from October 1 onwards, it seems fine to promise that you'll actually do CT for all certs with a notBefore of September 24 or later, and on October 1, you will stop issuing certs with a notBefore earlier than September 24. (Of course the complexity now re-introduces some room for "honest" mistakes.)