Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(308)

Unified Diff: net/cert/sct_status_flags.h

Issue 2294373002: Certificate Transparency: Remove the obsolete invalid sct status. (Closed)
Patch Set: Created 4 years, 4 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
Index: net/cert/sct_status_flags.h
diff --git a/net/cert/sct_status_flags.h b/net/cert/sct_status_flags.h
index cdd63b9ffb2181e1fa1b60f43aa53769513a3e2e..ac0bc7d7e6716793c9911833fc089eff881818a9 100644
--- a/net/cert/sct_status_flags.h
+++ b/net/cert/sct_status_flags.h
@@ -21,12 +21,9 @@ enum SCTVerifyStatus {
// The SCT is from an unknown log, so we cannot verify its signature.
SCT_STATUS_LOG_UNKNOWN = 1,
- // This value is deprecated and should not be used. It has been split
- // into INVALID_SIGNATURE and INVALID_TIMESTAMP to represent the
- // different reasons an SCT could be invalid. Though it is no longer
- // in use, it is preserved here because it may be present in
- // serialized messages.
- SCT_STATUS_INVALID = 2,
+ // SCTVerifyStatus=2 used to represent SCT_STATUS_INVALID, which has now been
+ // split into INVALID_SIGNATURE and INVALID_TIMESTAMP to represent the
+ // different reasons an SCT could be invalid.
Ryan Sleevi 2016/09/01 00:01:29 // Obsolete. Kept here to avoid reuse. // SCT_STAT
Eran Messeri 2016/09/01 14:16:34 Done.
// The SCT is from a known log, and the signature is valid.
SCT_STATUS_OK = 3,

Powered by Google App Engine
This is Rietveld 408576698