Re: [Bug-wget] [bug #43799] wget should implement OCSP + OCSP stapling

[Tim Ruehsen]

On Wednesday 19 August 2015 18:19:16 Petr Pisar wrote:
> On Wed, Aug 19, 2015 at 03:37:06PM +0000, Tim Ruehsen wrote:
> > Regarding MITM and other attacks... did you notice that OCSP responder
> > URLs
> > are HTTP (plain text) will all the insecurity ? I never saw a HTTPS URL,
> > did you ?

> 
> There is no need for HTTPS. The OCSP response is signed by the CA's OCSP
> responder. So the problem of OCSP response integrity reduces to verifying
> the OCSP response signature. Of course to verify the signature, one needs
> to verify OCSP responder's certificate. But this is the same story as with
> CRLs.

A signature makes it possible to verify the delivered content (answer from 
OCSP responder here), and - as you say - is as trustworthy as the CA certs you 
have.
But there also is a privacy concern involved when using plain text 
communication. The OCSP request data holds unique parts of the server 
certificate(s). Anyone (between me and the OCSP responder) can see and assign 
my IP with the domain (or at least with the server IP) that I want to access. 
OCSP stapling is a big win here, but is potential useless if the server has a 
cert chain. That's why I want to see OCSP multi-stapling in the near future 
(RFC6961 TLS Multiple Certificate Status Request Extension). That's also a big 
HTTPS connect speedup. AFAIK, there is no TLS library currently supporting it.

Tim

signature.asc
Description: This is a digitally signed message part.