Remove support for 'system' SSL on Mac (SecureTransport) and Win (SChannel)

content/browser/browser_main_loop.cc

Index: content/browser/browser_main_loop.cc
diff --git a/content/browser/browser_main_loop.cc b/content/browser/browser_main_loop.cc
index 255e63a3eceb6309456daaeaa7027b1941e10313..b58a2cb2267779a56d004a1b0aa6ba3c07f5f733 100644
--- a/content/browser/browser_main_loop.cc
+++ b/content/browser/browser_main_loop.cc
@@ -279,24 +279,8 @@ void BrowserMainLoop::EarlyInitialization() {
 #endif
 
 #if !defined(USE_OPENSSL)
-  // Use NSS for SSL by default.
-  // The default client socket factory uses NSS for SSL by default on
-  // Windows and Mac.
-  bool init_nspr = false;
-#if defined(OS_WIN) || defined(OS_MACOSX)
-  if (parsed_command_line_.HasSwitch(switches::kUseSystemSSL)) {
-    net::ClientSocketFactory::UseSystemSSL();
-  } else {
-    init_nspr = true;
-  }
-  UMA_HISTOGRAM_BOOLEAN("Chrome.CommandLineUseSystemSSL", !init_nspr);
-#elif defined(USE_NSS)
-  init_nspr = true;
-#endif
-  if (init_nspr) {
-    // We want to be sure to init NSPR on the main thread.
-    crypto::EnsureNSPRInit();
-  }
+  // We want to be sure to init NSPR on the main thread.

[wtc, 2013/01/15 23:50:22]

It is useful to keep the "Use NSS for SSL" part of the
original comment, so that we know why we need to initialize
NSPR.

[Ryan Sleevi, 2013/01/15 23:57:45]

We still need to initialize NSPR for Crypto - independent of the SSL bit. That's
why I removed it.

[wtc, 2013/01/16 00:36:03]

Ah, you're right.

+  crypto::EnsureNSPRInit();
 #endif  // !defined(USE_OPENSSL)
 
 #if defined(OS_POSIX) && !defined(OS_MACOSX) && !defined(OS_ANDROID)