On 08/08/16 10:25, Rob Stradling wrote:
<snip>
Nick, Peter,

I looked at https://crt.sh/mozilla-disclosures immediately after the
Symantec cross-cert expired, and I was surprised to see no change.  I
was on holiday all last week, so I'm only just investigating it properly
now.

I suspect crt.sh is getting confused by the combination of the expired
Symantec cross-cert and the revoked Identrust cross-cert.  If they'd
both expired or both been revoked, I suspect this (presumed) bug would
not have been discovered.

I'm going to try changing
  "Unconstrained, but all observed paths Revoked"
to
  "Unconstrained, but all unexpired observed paths Revoked"

Bug fixed.

All of the FPKI intermediates now show up in this group:
https://crt.sh/mozilla-disclosures#trustrevoked

Note that crt.sh says "Disclosure is probably required!" for this group, as per Richard's suggestion to "err on the side of disclosing subordinates under a revoked certificate, with exceptions..." [1].

Richard did say he'd "be willing to make an exception for this specific case, since the Federal Bridge is a known issue" [2].

Kathleen,
Would it be possible to add a field (to Salesforce and to https://mozillacaprogram.secure.force.com/CA/PublicIntermediateCertsRevokedCSVFormat) so that crt.sh can track these exceptions?


[1] https://www.mail-archive.com/[email protected]/msg03468.html

[2] https://www.mail-archive.com/[email protected]/msg03476.html

--
Rob Stradling
Senior Research & Development Scientist
COMODO - Creating Trust Online

_______________________________________________
dev-security-policy mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-security-policy

Reply via email to