3 ms·

Actually, Firefox is going to start sending a CRL 4x daily in lieu of OCSP. Chrome hasn't supported OCSP since 2012, and publishes CRLSets instead. OCSP is co

by wffurr 6y ago

Actually, Firefox is going to start sending a CRL 4x daily in lieu of OCSP. Chrome hasn't supported OCSP since 2012, and publishes CRLSets instead. OCSP is considered bad by at least Chrome and Firefox due to leaking side channel information in exactly the way the article describes. https://blog.mozilla.org/security/2020/01/21/crlite-part-3-speeding-up-secure-browsing/ https://blog.mozilla.org/security/2020/01/21/crlite-part-3-s... https://www.imperialviolet.org/2012/02/05/crlsets.html https://www.imperialviolet.org/2012/02/05/crlsets.html

majewsky 6y ago
And for websites, there's a better way to do OCSP. The web server using the certificate can get an OCSP response for itself (usually once every few minutes) and attach it to all TLS handshakes for that same domain ("OCSP stapling"). That way, clients get an up-to-date OCSP response, but without having to reveal their browsing behavior to the OCSP server. Unfortunately, there is no obvious way to carry over this behavior to application binaries, since we're not dealing with a client-server architecture here.