Opened 6 years ago

Last modified 3 years ago

#6802 enhancement new

TLS: support OCSP stapling

Reported by: Tobias Oberstein Owned by:
Priority: normal Milestone:
Component: core Keywords: TLS, pyOpenSSL, OCSP
Cc: Adi Roiban, jonathan@… Branch:


Quoting from [here]

OCSP stapling, formally known as the TLS Certificate Status Request extension, is an alternative approach to the Online Certificate Status Protocol (OCSP) for checking the revocation status of X.509 digital certificates.

In short, this provides two advantages:

The TLS extensions is defined in [this RFC] and supported by a few servers like [Nginx]

In OpenSSL, there once was a [vulnarability] that got fixed [here]

For OpenSSL based servers, usage can be seen here:

Providing support for OCSP stapling in Twisted would be great, though non-trivial. A prerequisite would be exposing the relevant bits in pyOpenSSL.

Some more info:

Change History (3)

comment:1 Changed 5 years ago by Hynek Schlawack

Given I find this rather low-priority.

comment:2 Changed 4 years ago by Adi Roiban

Cc: Adi Roiban added

The referred articles concludes with

If we want a scalable solution to the revocation problem then it's probably going to come in the form of short-lived certificates or something like OCSP Must Staple.

OCSP Must Staple is essentially creating short-lived certificates.

I think that Adam Langley only takes into account TLS usage in web browsers over public networks.

I have created tickets for python cryptography ... as pyopenssl depends on them:

maybe we will also need to implement this in pyopenssl once cryptography provides this.

comment:3 Changed 3 years ago by Jonathan Stoppani

Cc: jonathan@… added
Note: See TracTickets for help on using tickets.