Don't use no_new_privs mode when running NM process on Linux

chrome/browser/extensions/api/messaging/native_process_launcher_posix.cc

Index: chrome/browser/extensions/api/messaging/native_process_launcher_posix.cc
diff --git a/chrome/browser/extensions/api/messaging/native_process_launcher_posix.cc b/chrome/browser/extensions/api/messaging/native_process_launcher_posix.cc
index 2a75aba1d3903069df5db39c7333a9093a662c79..1516fa394034f00135e2b893489ba892f3a854ad 100644
--- a/chrome/browser/extensions/api/messaging/native_process_launcher_posix.cc
+++ b/chrome/browser/extensions/api/messaging/native_process_launcher_posix.cc
@@ -74,6 +74,10 @@ bool NativeProcessLauncher::LaunchNativeProcess(
 
   base::LaunchOptions options;
   options.fds_to_remap = &fd_map;
+
+  // Don't use no_new_privs mode, e.g. in case the host needs to use sudo.

[Lambros, 2014/05/29 01:52:28]

Is "host" the right terminology?

[Sergey Ulanov, 2014/05/29 01:57:59]

Yes. Native Messaging Host.

+  options.allow_new_privs = true;

[jln (very slow on Chromium), 2014/05/29 19:18:58]

As discussed in the bug, let's scope this to non Chrome OS only.

[Sergey Ulanov, 2014/05/29 19:57:39]

Done.

[Sergey Ulanov, 2014/05/29 19:59:38]

Please note that currently this code is never executed on Chrome OS (but it may
be useful in the future to fix crbug.com/334087).

+
   if (!base::LaunchProcess(command_line, options, process_handle)) {
     LOG(ERROR) << "Error launching process";
     return false;