3 ms·
It's on the order of a few hundred bytes, only happens on the first connection, and is still orders of magnitude faster and more effective than the alternative
by mholt 4y ago
It's on the order of a few hundred bytes, only happens on the first connection, and is still orders of magnitude faster and more effective than the alternative (no stapling, which requires the client to make separate round-trips to a third party service which has all sorts of other problems).
OCSP stapling is temporary, anyway: just until we get certificate lifetimes short enough to make revocation irrelevant.*
* This is how it should be, but the industry seems to be going the direction of keeping cert lifetimes longer.
- aaomidi 4y agoA few hundred bytes is a ton data for something that a lot of people don’t particularly care about, and is still broken despite OCSP stapling. People don’t have low latency, clean internet all over the world and adding something like this on top of an already pretty bloated negotiation doesn’t help. As for the alternative not a single browser out there validates OCSP out of the box on the hot path (e.g actually waits for OCSP before proceeding)
- OrvalWintermute 4y agoThis is a brower problem, but it is configurable.
- OrvalWintermute 4y agoSpeaking from a PKI perspective you may head towards shorter lived certificates in many use-cases, NPE / automatable re-keying being examples of that. However, for strong PKI on a consumer or enterprise encryption/decryption device, e.g. smartcards, there is big costs associated with shortening lifetimes. Not going to fly there.