openssl/crypto/ct
Rob Percival a6f5d614c5 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 <matt@openssl.org>
Reviewed-by: Rich Salz <rsalz@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/1407)
2016-08-05 21:34:59 -04:00
..
build.info CT policy validation 2016-03-01 20:03:25 +00:00
ct_b64.c Mkae CT_log_new_from_base64 always return 0 on failure 2016-08-05 21:34:59 -04:00
ct_err.c Removes CTLOG_new_null from the CT public API 2016-08-05 18:49:58 -04:00
ct_locl.h Specify array sizes 2016-06-11 16:43:49 +02:00
ct_log.c Removes CTLOG_new_null from the CT public API 2016-08-05 18:49:58 -04:00
ct_oct.c Fix potential access of null pointer (pp) 2016-06-07 12:21:46 -04:00
ct_policy.c Copyright consolidation 07/10 2016-05-17 14:51:26 -04:00
ct_prn.c Copyright consolidation 07/10 2016-05-17 14:51:26 -04:00
ct_sct_ctx.c Copyright consolidation 07/10 2016-05-17 14:51:26 -04:00
ct_sct.c Fix some style issues... 2016-08-02 09:59:23 +02:00
ct_vfy.c Copyright consolidation 07/10 2016-05-17 14:51:26 -04:00
ct_x509v3.c Specify array sizes 2016-06-11 16:43:49 +02:00