diff options
| author | Rob Percival <robpercival@google.com> | 2016-08-23 18:30:18 +0100 |
|---|---|---|
| committer | Matt Caswell <matt@openssl.org> | 2016-08-24 13:58:19 +0100 |
| commit | 513a3cb16b256a5289f8441c21eebbc7f5feef9a (patch) | |
| tree | 8b100ca7e3c5a680b4ce38629bc5ae9e3a291ad8 | |
| parent | e12981019aa44d162a5ec553a1cfadf3b5754c9a (diff) | |
Correct documentation about SCT setters resetting validation status
Reviewed-by: Rich Salz <rsalz@openssl.org>
Reviewed-by: Matt Caswell <matt@openssl.org>
| -rw-r--r-- | doc/crypto/SCT_new.pod | 4 |
1 files 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<SCT_verify(3)>). +All of the setters will reset the validation status of the SCT to +SCT_VALIDATION_STATUS_NOT_SET (see L<SCT_validate(3)>). 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. |