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..6b8998ca6548542d664f3f29c1c0c21292ae2d02 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,12 @@ bool NativeProcessLauncher::LaunchNativeProcess(
 
   base::LaunchOptions options;
   options.fds_to_remap = &fd_map;
+
+#if !defined(OS_CHROMEOS)
+  // Don't use no_new_privs mode, e.g. in case the host needs to use sudo.
+  options.allow_new_privs = true;
+#endif
+
   if (!base::LaunchProcess(command_line, options, process_handle)) {
     LOG(ERROR) << "Error launching process";
     return false;