Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I was initially shocked by this as well so I did some more reading on OCSP and it seems this is being addressed through OCSP stapling.

According to Wikipedia "[OCSP stapling] allows the presenter of a certificate to bear the resource cost involved in providing Online Certificate Status Protocol (OCSP) responses by appending ("stapling") a time-stamped OCSP response signed by the CA to the initial TLS handshake, eliminating the need for clients to contact the CA, with the aim of improving both security and performance."

I'm not aware how widely deployed OCSP stapling is in reality. I looked at my Firefox settings which seemed to be the default for OCSP and it looked like this:

  security.OCSP.enabled                     1
  security.OCSP.require                     false
  security.OCSP.timeoutMilliseconds.hard    10000
  security.OCSP.timeoutMilliseconds.soft    2000
  security.ssl.enable_ocsp_must_staple      true
  security.ssl.enable_ocsp_stapling         true
So I assume OCSP stapling is enabled but direct OCSP is disabled in Firefox by default but a positive OCSP response is not required in general. I tried to check what was really happening with Wireshark but regardless of the configuration and sites I visited, I couldn't get Firefox to emit an OCSP query.

I also don't know what other TLS implementations (like OpenSSL) do and how users of such libraries usually configure them.

Addendum: Oh and of course, OCSP stapling is useless when you weren't about to open a TLS connection (like in this case when checking software signing certificates). I'm also curious if and how this works for other applications of X.509 certificates such as mutual TLS authentication.



Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: