Certificate Transparency: Threading the CT verifier into the SSL client socket.

chrome/browser/profiles/profile_impl_io_data.cc

Index: chrome/browser/profiles/profile_impl_io_data.cc
diff --git a/chrome/browser/profiles/profile_impl_io_data.cc b/chrome/browser/profiles/profile_impl_io_data.cc
index 6eb37674fb33f30daccf9553d64d724595cec7c6..c5c383eb2f037c1f56af0c20fcb520a5cdd26774 100644
--- a/chrome/browser/profiles/profile_impl_io_data.cc
+++ b/chrome/browser/profiles/profile_impl_io_data.cc
@@ -371,6 +371,8 @@ void ProfileImplIOData::InitializeInternal(
 
   main_context->set_host_resolver(
       io_thread_globals->host_resolver.get());
+  main_context->set_cert_transparency_verifier(
+      io_thread_globals->cert_transparency_verifier.get());

[wtc, 2013/11/26 01:47:23]

Recall that I suggested you imitate the code that handles
transport_security_state? I am wondering why this class is not getting
transport_security_state from io_thread_globals (see line 364).

[Ryan Sleevi, 2013/11/26 02:22:14]

This is unrelated. But that's because transport_security_state contains
per-profile information (it's a persistent layer). The SCT verifier state does
not itself cache anything that would leak data between profiles.

[Eran M. (Google), 2013/11/26 14:45:53]

Ack - I understand it should be left as it's now.

   main_context->set_http_auth_handler_factory(
       io_thread_globals->http_auth_handler_factory.get());