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) --- util/libcrypto.num | 1 - 1 file changed, 1 deletion(-) (limited to 'util') diff --git a/util/libcrypto.num b/util/libcrypto.num index 0c7cd9a8c0..a02cc8de76 100644 --- a/util/libcrypto.num +++ b/util/libcrypto.num @@ -3484,7 +3484,6 @@ EVP_OpenFinal 3432 1_1_0 EXIST::FUNCTION:RSA RAND_egd_bytes 3433 1_1_0 EXIST::FUNCTION:EGD UI_method_get_writer 3434 1_1_0 EXIST::FUNCTION:UI BN_secure_new 3435 1_1_0 EXIST::FUNCTION: -CTLOG_new_null 3436 1_1_0 EXIST::FUNCTION:CT SHA1_Update 3437 1_1_0 EXIST::FUNCTION: BIO_s_connect 3438 1_1_0 EXIST::FUNCTION:SOCK EVP_MD_meth_get_init 3439 1_1_0 EXIST::FUNCTION: -- cgit v1.2.3