Use NSS for symmetric key crypto operations on Windows and Mac.

chrome/renderer/chrome_render_process_observer.cc

Index: chrome/renderer/chrome_render_process_observer.cc
diff --git a/chrome/renderer/chrome_render_process_observer.cc b/chrome/renderer/chrome_render_process_observer.cc
index 4a2a97ca6b935d005ba7d836adfef03d94f31a44..561e425311173e894c97d3161bd00c97ce01ad7b 100644
--- a/chrome/renderer/chrome_render_process_observer.cc
+++ b/chrome/renderer/chrome_render_process_observer.cc
@@ -186,7 +186,8 @@ ChromeRenderProcessObserver::ChromeRenderProcessObserver(
 #endif
 
 #if defined(OS_POSIX) && !defined(OS_MACOSX) && defined(USE_NSS)
-  // Remoting requires NSS to function properly.
+  // On Linux, NSS uses system libraries, so the .so's must be loaded.

[Nick Bray, 2012/06/14 20:37:06]

On a side note, ChromeOS uses a patched version of NSS that behaves differently
than Linux in some cases.  I've been burned by this.  Probably not relevant for
this CL, but beware of NSS skew for ChromeOS hardware.

[Ryan Sleevi, 2012/06/14 20:54:48]

Do you have an example of this?

Chrome on Linux/CrOS makes no statements about what version the system NSS must
be. It uses shared objects for both of them. There are no patches to NSS that
Chrome for Linux uses.

+  // (On all platforms, RNG is primed in WebKit (for window.crypto.getRandom()).

[Ryan Sleevi, 2012/06/14 19:35:26]

You can remove this second comment.

[ddorwin, 2012/06/14 20:44:19]

Done.

   if (!command_line.HasSwitch(switches::kSingleProcess)) {
     // We are going to fork to engage the sandbox and we have not loaded
     // any security modules so it is safe to disable the fork check in NSS.