From 513a3cb16b256a5289f8441c21eebbc7f5feef9a Mon Sep 17 00:00:00 2001 From: Rob Percival Date: Tue, 23 Aug 2016 18:30:18 +0100 Subject: [PATCH] Correct documentation about SCT setters resetting validation status Reviewed-by: Rich Salz Reviewed-by: Matt Caswell --- doc/crypto/SCT_new.pod | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/crypto/SCT_new.pod b/doc/crypto/SCT_new.pod index a12408b265..4ee41a6d41 100644 --- a/doc/crypto/SCT_new.pod +++ b/doc/crypto/SCT_new.pod @@ -145,8 +145,8 @@ required for verifying the SCT. Some of the setters return int, instead of void. These will all return 1 on success, 0 on failure. They will not make changes on failure. -Most of the setters will reset the validation status of the SCT to -SCT_VALIDATION_STATUS_NOT_SET (see L). +All of the setters will reset the validation status of the SCT to +SCT_VALIDATION_STATUS_NOT_SET (see L). SCT_set_source() will call SCT_set_log_entry_type() if the type of certificate the SCT was issued for can be inferred from where the SCT was found. -- GitLab