OLD | NEW |
---|---|
(Empty) | |
1 // Copyright 2016 The Chromium Authors. All rights reserved. | |
2 // Use of this source code is governed by a BSD-style license that can be | |
3 // found in the LICENSE file. | |
4 #ifndef NET_CERT_CT_POLICY_STATUS_H | |
Ryan Sleevi
2016/02/18 06:46:51
There's supposed to be a newline between 3 & 4 (an
estark
2016/02/18 19:24:32
Done.
| |
5 #define NET_CERT_CT_POLICY_STATUS_H | |
6 | |
7 namespace net { | |
8 | |
9 namespace ct { | |
10 | |
11 // Information about a connection's compliance with the CT EV | |
12 // certificate policy. | |
13 enum EVPolicyCompliance { | |
Ryan Sleevi
2016/02/18 06:46:51
Do you want to enum class this so you can forward
estark
2016/02/18 19:24:32
Done.
| |
14 // The certificate was not EV, so the EV policy doesn't apply. | |
15 EV_POLICY_DOES_NOT_APPLY = 0, | |
Ryan Sleevi
2016/02/18 06:46:51
Do you still need this explicit numbering?
If you
estark
2016/02/18 19:24:31
I think I started UMAing it in a follow-up CL. I'l
| |
16 // The connection complied with the EV certificate policy by being | |
17 // included on the EV whitelist. | |
18 EV_POLICY_COMPLIES_VIA_WHITELIST, | |
19 // The connection complied with the EV certificate policy by | |
20 // including SCTs that satisfy the policy. | |
21 EV_POLICY_COMPLIES_VIA_SCTS, | |
22 // The connection did not have enough SCTs to retain its EV | |
23 // status. | |
24 EV_POLICY_NOT_ENOUGH_SCTS, | |
25 // The connection did not have diverse enough SCTs to retain its | |
26 // EV status. | |
27 EV_POLICY_NOT_DIVERSE_SCTS, | |
28 // The connection cannot be considered compliant because the build | |
29 // isn't timely and therefore log information might be out of date | |
30 // (for example a log might no longer be considered trustworthy). | |
31 EV_POLICY_BUILD_NOT_TIMELY, | |
32 }; | |
33 | |
34 } // namespace ct | |
35 | |
36 } // namespace net | |
37 | |
38 #endif // NET_CERT_CT_POLICY_STATUS_H | |
OLD | NEW |