Include both certificate chains in invalid cert reporting

chrome/browser/net/cert_logger.proto

 // Copyright (c) 2011 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 //
 // This protobuffer is intended to store reports from Chrome users of
 // certificate pinning errors. A report will be sent from Chrome when it gets
 // e.g. a certificate for google.com that chains up to a root CA not expected by
 // Chrome for that origin, such as DigiNotar (compromised in July 2011), or
 // other pinning errors such as a blacklisted cert in the chain. The
 // report from the user will include the hostname being accessed, 
@@ skipping 20 matching lines @@
   required string cert_chain = 2;
   // The time (in usec since the epoch) when the client attempted to access the
   // site generating the pinning error.
   required int64 time_usec = 3;
   // public_key_hash contains the string forms of the hashes calculated for
   // the chain. (I.e. "sha1/<base64 data>".)
   repeated string public_key_hash = 4;
   // pin contains the string forms of the pins that were matched against for
   // this host.
   repeated string pin = 5;
+  // The certificate chain as received by the client from the server. A
+  // series of PEM-encoded certificates, including intermediates but not
+  // necessarily the root.
+  optional string unverified_server_cert_chain = 6;
 };
 
 // The response sent back to the user.
 message CertLoggerResponse {
   enum ResponseCode {
     OK = 1;
     MALFORMED_CERT_DATA = 2;
     HOST_CERT_DONT_MATCH = 3;
     ROOT_NOT_RECOGNIZED = 4;
     ROOT_NOT_UNEXPECTED = 5;
     OTHER_ERROR = 6;
   };
   required ResponseCode response = 1;
 };