fetch-ocsp-response: Handle spurious openssl exist status 0
With OpenSSL <= 1.0.1, openssl ocsp command still returns exit code 0, even if verification was failed. If that happens certain string is emitted in stderr, so check that string and if exists, treat it as error. This issue was fixed in OpenSSL 1.0.2. At least OpenSSL 1.0.2, openssl ocsp command still returns exit code 0, even if responder returned non-successful status code (e.g., trylater(3)). We are not sure this is intentional or not. To handle this, we again check certain error string in stdout, and if it is found, treat it as error.
Showing
Please register or sign in to comment