Chromium Code Reviews| Index: net/base/net_log_event_type_list.h |
| diff --git a/net/base/net_log_event_type_list.h b/net/base/net_log_event_type_list.h |
| index 10d9c593b2f6b1376e5f7e13eb0c44fa044ba52f..c548b0c45f3ca6a15622382a119ffbafba9dcaef 100644 |
| --- a/net/base/net_log_event_type_list.h |
| +++ b/net/base/net_log_event_type_list.h |
| @@ -1883,6 +1883,40 @@ EVENT_TYPE(CERT_VERIFIER_REQUEST) |
| // This event is created when we start a CertVerifier job. |
| // The END phase event parameters are: |
| // { |
| +// "cert_status": <Bitmask of CERT_STATUS_* |
| +// from net/base/cert_status_flags.h> |
| +// "common_name_fallback_used": <True if a fallback to the common name |
| +// was used when matching the host |
| +// name, rather than using the |
| +// subjectAltName.> |
| +// "has_md2": <Property of the certificate chain.> |
| +// "has_md4": <Property of the certificate chain.> |
| +// "has_md5": <Property of the certificate chain.> |
| +// "is_issued_by_additional_trust_anchor": <True if the root CA used for |
| +// this |
| +// verification came from the list |
| +// of additional trust anchors.> |
|
Ryan Sleevi
2014/05/31 00:53:02
indentation issue on 1896 and 1900
mshelley
2014/05/31 01:50:39
Done. Sorry about all of that -- I think those lin
|
| +// "is_issued_by_known_root": <True if we recognise the root CA as a |
| +// standard |
| +// root. If it isn't then it's probably the |
| +// case that this certificate was generated by |
| +// a MITM proxy whose root has been installed |
| +// locally. This is meaningless if the |
| +// certificate |
| +// was not trusted.> |
|
Ryan Sleevi
2014/05/31 00:53:02
weird wrap.
mshelley
2014/05/31 01:50:39
Done.
|
| +// "public_key_hashes": <If the certificate was successfully verified then |
| +// this contains the hashes, in several hash |
| +// algorithms, |
| +// of the SubjectPublicKeyInfos of the chain.> |
| +// "verified_cert": <The certificate and chain that was constructed |
| +// during verification. Note that the though the verified |
| +// certificate will match the originally supplied |
| +// certificate, |
| +// the intermediate certificates stored within may be |
| +// substantially different. In the event of a verification |
| +// failure, this will contain the chain as supplied by the |
| +// server. This may be NULL if running within the |
| +// sandbox.> |
|
Ryan Sleevi
2014/05/31 00:53:02
weird wrapping here too.
mshelley
2014/05/31 01:50:39
Done.
|
| // "certificates": <A list of PEM encoded certificates, the first one |
| // being the certificate to verify and the remaining |
| // being intermediate certificates to assist path |