CA:ImprovingRevocation: Difference between revisions

Line 119: Line 119:
Once that happens, for all practical purposes, Firefox will not have anything to do with CRLs. The only exception is that, if you use some specialized tools to important CRLs into Firefox's certificate database, then Firefox will recognize those specially-imported CRLs for a while. However, it is likely that that will stop too, when we switch to the new certificate validation library.
Once that happens, for all practical purposes, Firefox will not have anything to do with CRLs. The only exception is that, if you use some specialized tools to important CRLs into Firefox's certificate database, then Firefox will recognize those specially-imported CRLs for a while. However, it is likely that that will stop too, when we switch to the new certificate validation library.


* Discussion: [https://groups.google.com/d/msg/mozilla.dev.security.policy/zgXqG_P3RIg/RozDfvB5t04J In mozilla.dev.security.policy]
* Discussion: [https://groups.google.com/d/msg/mozilla.dev.security.policy/zgXqG_P3RIg/RozDfvB5t04J mozilla.dev.security.policy]


* Code Change: {{Bug|585122#c34}}
* Code Change: {{Bug|585122#c34}}


* Dependencies:  
* Dependencies: [[CA:ImprovingRevocation#Remove_CRL_User-Interface | Remove CRL User-Interface]].


* Policy Change: Remove any reference to CRLs from [http://www.mozilla.org/projects/security/certs/policy/ Mozilla's CA Certificate Policy].
* Policy Change: Remove any reference to CRLs from [http://www.mozilla.org/projects/security/certs/policy/ Mozilla's CA Certificate Policy].
Confirmed users, Administrators
5,526

edits