<?xml version="1.0" encoding='utf-8'?>
<!DOCTYPE wml PUBLIC "-//WAPFORUM//DTD WML 1.1//EN" "http://www.wapforum.org/DTD/wml_1.1.xml">
<wml>
<card id="card1" title="Certificate revocation - Page 2 - Wikipedia">
<p>
<a accesskey="1" href="page.php?w=certificate_revocation&amp;p=1">1.Previous</a><br />
<a accesskey="3" href="page.php?w=certificate_revocation&amp;p=3">3.Next</a>
</p>
<p>which produces a <a href="page.php?w=cryptographically_authenticated">cryptographically authenticated</a> statement of revocation.</p>

<p>For distributing revocation information to clients, the timeliness of the discovery of revocation (and hence the window for an attacker to exploit a compromised certificate) trades off against resource usage in querying revocation statuses and privacy concerns. If revocation information is unavailable (either due to an accident or an attack), clients must decide whether to fail-hard and treat a certificate</p><p>
<a accesskey="1" href="page.php?w=certificate_revocation&amp;p=1">1.Previous</a><br />
<a accesskey="3" href="page.php?w=certificate_revocation&amp;p=3">3.Next</a>
</p>

<do type="prev" label="Search">
        <go href="search.wml"/>
</do>

</card>
</wml>
