Behaviour facing a broken OCSP responder

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Behaviour facing a broken OCSP responder
From: rsalz@xxxxxxxxxx (Salz, Rich)
Date: Mon, 14 Sep 2015 20:26:01 +0000
In-reply-to: <6d191f8cad2f694f8439d4cc29c6e9a9@teksavvy.com>
References: <f2cba3bec87a090a2cac7b8ba5d93261@teksavvy.com> <c9f74981aa2642caae26fe147f3f3880@ustx2ex-dag1mb3.msg.corp.akamai.com> <6d191f8cad2f694f8439d4cc29c6e9a9@teksavvy.com>

 
> Are these the only three error codes ?

Nope.  It's not standardized at all sadly

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

References:
- Behaviour facing a broken OCSP responder
  - From: jonetsu
- Behaviour facing a broken OCSP responder
  - From: Salz, Rich
- Behaviour facing a broken OCSP responder
  - From: jonetsu

Prev by Date: Behaviour facing a broken OCSP responder
Next by Date: Question about Openssl FIPS module and Python-openssl
Previous by thread: Behaviour facing a broken OCSP responder
Next by thread: Question about Openssl FIPS module and Python-openssl
Index(es):
- Date
- Thread

[Index of Archives] [Linux ARM Kernel] [Linux ARM] [Linux Omap] [Fedora ARM] [IETF Annouce] [Security] [Bugtraq] [Linux] [Linux OMAP] [Linux MIPS] [ECOS] [Asterisk Internet PBX] [Linux API]

Powered by Linux