Re: [openssl-users] Behaviour facing a broken OCSP responder

2015-09-14 Thread Salz, Rich
> Are these the only three error codes ? Nope. It's not standardized at all sadly ___ openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users

Re: [openssl-users] Behaviour facing a broken OCSP responder

2015-09-14 Thread jonetsu
> From: "Salz, Rich" > Date: 09/14/15 16:07 > Are you talking about the command-line? Yes. > It would be great if someone sent in a patch that standardized > and documented exit codes, like 0 for got a "good" > response, "1" for got a "bad" response, and 10 for got an > unparseable response

Re: [openssl-users] Behaviour facing a broken OCSP responder

2015-09-14 Thread Salz, Rich
> The documentation does not seem too clear about what the behaviour > exactly is when OpenSSL deals with a broken OCSP responder.  For instance, > one that would send an OK without any contents.  We call openssl from an > application and would like to know what is returned in such a case, or in th

[openssl-users] Behaviour facing a broken OCSP responder

2015-09-14 Thread jonetsu
Hello, The documentation does not seem too clear about what the behaviour exactly is when OpenSSL deals with a broken OCSP responder.  For instance, one that would send an OK without any contents.  We call openssl from an application and would like to know what is returned in such a case, or i