On 18/06/12 11:40, Rob Stradling wrote:
On 16/06/12 23:31, Dr. Stephen Henson wrote:
snip
Is there a way to patch httpd so that it can work around the
limitations in the OpenSSL API and always send the correct OCSP
Response?
Possible changes to OpenSSL:
Should the Stapling Callback function be
On 16/06/12 23:31, Dr. Stephen Henson wrote:
snip
Is there a way to patch httpd so that it can work around the
limitations in the OpenSSL API and always send the correct OCSP
Response?
Possible changes to OpenSSL:
Should the Stapling Callback function be called later in the
handshake (perhaps
Using OpenSSL 1.x and Apache httpd 2.4.x, I've been trying to get OCSP
Stapling to work with both an RSA cert and an ECC cert configured. The
desired behaviour is (obviously) that httpd should staple the correct
OCSP Response for whichever cert (RSA or ECC) it chooses to send to the
client.
On Fri, Jun 15, 2012, Rob Stradling wrote:
Using OpenSSL 1.x and Apache httpd 2.4.x, I've been trying to get
OCSP Stapling to work with both an RSA cert and an ECC cert
configured. The desired behaviour is (obviously) that httpd should
staple the correct OCSP Response for whichever cert (RSA
On Sat, Jun 16, 2012, Dr. Stephen Henson wrote:
On Fri, Jun 15, 2012, Rob Stradling wrote:
Using OpenSSL 1.x and Apache httpd 2.4.x, I've been trying to get
OCSP Stapling to work with both an RSA cert and an ECC cert
configured. The desired behaviour is (obviously) that httpd should
