From a6f5d614c53aaa58595af4998228e82404132739 Mon Sep 17 00:00:00 2001 From: Rob Percival Date: Fri, 5 Aug 2016 21:27:12 -0400 Subject: Mkae CT_log_new_from_base64 always return 0 on failure In one failure case, it used to return -1. That failure case (CTLOG_new() returning NULL) was not usefully distinct from all of the other failure cases. Reviewed-by: Matt Caswell Reviewed-by: Rich Salz (Merged from https://github.com/openssl/openssl/pull/1407) --- crypto/ct/ct_b64.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'crypto') diff --git a/crypto/ct/ct_b64.c b/crypto/ct/ct_b64.c index 80bd45e..d13d8f2 100644 --- a/crypto/ct/ct_b64.c +++ b/crypto/ct/ct_b64.c @@ -149,7 +149,7 @@ int CTLOG_new_from_base64(CTLOG **ct_log, const char *pkey_base64, const char *n *ct_log = CTLOG_new(pkey, name); if (*ct_log == NULL) { EVP_PKEY_free(pkey); - return -1; + return 0; } return 1; -- cgit v1.1