Revocation Checking and Chrome's CRL¶
Langley, A. (2012). Revocation Checking and Chrome's CRL. ImperialViolet.
Cited by¶
1 citation across 1 artifact.
Each citation links to the sentence it supports in the citing article.
Mechanisms¶
- Revocation Status Check
- If the responder is unreachable and the client soft-fails — treating "couldn't check" as "not revoked" so the page still loads — the entire control silently evaporates exactly when an attacker who has blocked the responder needs it to.
This sourceExplains that soft-fail revocation checking treats an unreachable responder as nonfatal, allowing an attacker who blocks the check to suppress revocation protection.
- If the responder is unreachable and the client soft-fails — treating "couldn't check" as "not revoked" so the page still loads — the entire control silently evaporates exactly when an attacker who has blocked the responder needs it to.
Verification¶
Does it exist? Not checked yet. This entry carries no identifier to resolve. It was extracted from the citation as written in the article, normalized, and deduplicated against the rest of the registry.
Does it back the claim? Not recorded. The single citation of this work carries no recorded support check.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Registry ID ref:ff55c3e96da8 · see in the full table