summaryrefslogtreecommitdiffstats
path: root/net/base/cert_verify_result.h
diff options
context:
space:
mode:
authorpalmer@chromium.org <palmer@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2012-08-08 06:32:23 +0000
committerpalmer@chromium.org <palmer@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2012-08-08 06:32:23 +0000
commitbc0d7b86f1bb6ed7a4e0374a2c1a4c8182de307c (patch)
tree6f86b2850f0763210ab249fceafbfb28a6013ead /net/base/cert_verify_result.h
parent77d555c7a0984ab10edc3d05016246d932cef2e1 (diff)
downloadchromium_src-bc0d7b86f1bb6ed7a4e0374a2c1a4c8182de307c.zip
chromium_src-bc0d7b86f1bb6ed7a4e0374a2c1a4c8182de307c.tar.gz
chromium_src-bc0d7b86f1bb6ed7a4e0374a2c1a4c8182de307c.tar.bz2
Revert 150375 - Implement SHA-256 fingerprint support
The HTTP-based Public Key Pinning Internet Draft (tools.ietf.org/html/draft-ietf-websec-key-pinning) requires this. Per wtc, give the *Fingeprint* types more meaningful *HashValue* names. Cleaning up lint along the way. BUG=117914 TEST=net_unittests, unit_tests TransportSecurityPersisterTest Review URL: https://chromiumcodereview.appspot.com/10825211 TBR=palmer@chromium.org Review URL: https://chromiumcodereview.appspot.com/10836150 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@150507 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'net/base/cert_verify_result.h')
-rw-r--r--net/base/cert_verify_result.h13
1 files changed, 4 insertions, 9 deletions
diff --git a/net/base/cert_verify_result.h b/net/base/cert_verify_result.h
index 0d33ed9..06baad2 100644
--- a/net/base/cert_verify_result.h
+++ b/net/base/cert_verify_result.h
@@ -45,15 +45,10 @@ class NET_EXPORT CertVerifyResult {
bool has_md5_ca;
bool has_md2_ca;
- // If the certificate was successfully verified then this contains the
- // fingerprints, in several hash algorithms, of the SubjectPublicKeyInfos
- // of the chain. The fingerprint from the leaf certificate will be the
- // first element of each sub-vector.
- //
- // This is a vector of vectors: Index the outer vector with
- // FingerprintTag, and then the inner HashValueVectors will be
- // fingerprints made with the algorithm named by the FingerprintTag.
- std::vector<HashValueVector> public_key_hashes;
+ // If the certificate was successfully verified then this contains the SHA1
+ // fingerprints of the SubjectPublicKeyInfos of the chain. The fingerprint
+ // from the leaf certificate will be the first element of the vector.
+ std::vector<SHA1Fingerprint> public_key_hashes;
// is_issued_by_known_root is 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