DO NOT REVIEW: Certificate Transparency: Extend SCT verify result enum.

tools/metrics/histograms/histograms.xml

Index: tools/metrics/histograms/histograms.xml
diff --git a/tools/metrics/histograms/histograms.xml b/tools/metrics/histograms/histograms.xml
index 25bab1dec629acb8992e973b0322a630bc709dac..d13ae5dcebcb9927499318d36837518fe522e09c 100644
--- a/tools/metrics/histograms/histograms.xml
+++ b/tools/metrics/histograms/histograms.xml
@@ -90128,8 +90128,9 @@ To add a new entry, add it with any value and run test to compute valid value.
 <enum name="SCTVerifyStatus" type="int">
   <int value="0" label="SCT_STATUS_NONE"/>
   <int value="1" label="SCT_STATUS_LOG_UNKNOWN"/>
-  <int value="2" label="SCT_STATUS_INVALID"/>
+  <int value="2" label="SCT_STATUS_INVALID_SIGNATURE"/>

[Ryan Sleevi, 2016/08/03 19:19:40]

This does the thing I mentioned on the thread that I didn't think we should do
:)

Which is, it changes the semantic meaning of this value (that is,
INVALID_SIGNATURE is a sub-category of INVALID)

The extent of implications here are primarily because it makes it difficult to
compare ver X to Y, because in version X, it means one thing, and version Y, it
means something different.

   <int value="3" label="SCT_STATUS_OK"/>
+  <int value="4" label="SCT_STATUS_INVALID_TIMESTAMP"/>
 </enum>
 
 <enum name="SdchDictionaryFate" type="int">