Split cert reporter class into report building/serializing and sending

chrome/browser/net/encrypted_cert_logger.proto

Index: chrome/browser/net/encrypted_cert_logger.proto
diff --git a/chrome/browser/net/encrypted_cert_logger.proto b/chrome/browser/net/encrypted_cert_logger.proto
new file mode 100644
index 0000000000000000000000000000000000000000..6c6274ebe4d943b982c9c0931ea28a130d184c21
--- /dev/null
+++ b/chrome/browser/net/encrypted_cert_logger.proto
@@ -0,0 +1,30 @@
+// Copyright 2015 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.
+//
+
+syntax = "proto2";
+
+package chrome_browser_net;
+
+// Chrome requires this.
+option optimize_for = LITE_RUNTIME;
+
+// This protobuffer is intended to store an encrypted report of an
+// invalid certificate chain.
+message EncryptedCertLoggerRequest {
+  // An encrypted, serialized CertLoggerRequest
+  required bytes encrypted_report = 1;
+  // The server public key version that was used to derive the shared secret.
+  required uint32 server_public_key_version = 2;
+  // The client public key that corresponds to the private key that was used
+  // to derive the shared secret.
+  required bytes client_public_key = 3;
+  // The encryption algorithm used to encrypt the report.
+  enum Algorithm {
+    UNKNOWN_ALGORITHM = 0;

[eroman, 2015/05/12 00:27:51]

when is 0 intended to be used?

[estark, 2015/05/12 20:42:16]

Good question... I sort of copied this from the corresponding server-side
protobuf without thinking too much about it. 

+    AEAD_ECDH_AES_128_CTR_HMAC_SHA256 = 1;
+  }
+  optional Algorithm algorithm = 4
+      [default = AEAD_ECDH_AES_128_CTR_HMAC_SHA256];
+};