Use ChannelMojo between the remoting daemon and network processes.

remoting/host/switches.cc

 // Copyright 2014 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #include "remoting/host/switches.h"
 
 namespace remoting {
 
 const char kDaemonPipeSwitchName[] = "daemon-pipe";
 const char kElevateSwitchName[] = "elevate";
 const char kHelpSwitchName[] = "help";
 const char kProcessTypeSwitchName[] = "type";
 const char kQuestionSwitchName[] = "?";
 const char kVersionSwitchName[] = "version";
 
 const char kProcessTypeController[] = "controller";
 const char kProcessTypeDaemon[] = "daemon";
 const char kProcessTypeDesktop[] = "desktop";
 const char kProcessTypeHost[] = "host";
 const char kProcessTypeRdpDesktopSession[] = "rdp_desktop_session";
 
 const char kParentWindowSwitchName[] = "parent-window";
 
 const char kInputSwitchName[] = "input";
 const char kOutputSwitchName[] = "output";
 
+const char kMojoPipeToken[] = "mojo-pipe-token";

[Sergey Ulanov, 2016/10/20 17:21:30]

Is this token used to limit access to the pipe? If so is it a problem that other
processes will be able to see the command line?

[Sam McNally, 2016/10/20 22:40:22]

Establishing a usable mojo connection between two processes has two layers. The
first establishes the physical connection over a pipe/socket; the second
(glossing over some details) has each process create one end of a message pipe
associated with a shared string, which the child sends to the parent to glue the
ends together. This token is that string.

The token could be used by another process, but only if it already had a
connection to the parent process.

The best reference I know if for this is the comments in
https://cs.chromium.org/chromium/src/mojo/edk/embedder/embedder.h?l=174.

+
 }  // namespace remoting