Enable pairing registry in me2me native messaging host on Windows

Enable pairing registry in me2me native messaging host on Windows:
1. Build a standalone remoting_native_messaging_host.exe. remoting_host.exe is a win32 application (as opposed to console application) thus not suitable as a native messaging host.
2. Initialize the pairing registry reg keys in the native messaging host.
3. GetPairdClients doesn't require elevation.
4. Add the native messaging host binary and manifest and the pairing reg keys to the installer.


Enable pairing registry in Me2Me native messaging host on Windows.

BUG=325567
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=251137

[weitao, 2014-02-13 01:31:55]

PTAL

[Sergey Ulanov, 2014-02-13 01:53:23]

LGTM once my comments are addressed

https://codereview.chromium.org/143303007/diff/1/remoting/host/installer/win/...
File remoting/host/installer/win/chromoting.wxs (right):

https://codereview.chromium.org/143303007/diff/1/remoting/host/installer/win/...
remoting/host/installer/win/chromoting.wxs:192: <File
Id="remoting_native_messaging_host.exe"
maybe call it native_messaging_host.exe? without remoting_ prefix.

https://codereview.chromium.org/143303007/diff/1/remoting/host/pairing_regist...
File remoting/host/pairing_registry_delegate_win.h (right):

https://codereview.chromium.org/143303007/diff/1/remoting/host/pairing_regist...
remoting/host/pairing_registry_delegate_win.h:30: const wchar_t
kPrivilegedKeyName[] = L"secrets";
rename this and kUnprivilegedKeyName to make it clear it's used for pairing
registry

https://codereview.chromium.org/143303007/diff/1/remoting/remoting_host.gypi
File remoting/remoting_host.gypi (right):

https://codereview.chromium.org/143303007/diff/1/remoting/remoting_host.gypi#...
remoting/remoting_host.gypi:655:
'host/setup/com.google.chrome.remote_desktop.json.jinja2',
I believe the previous order was correct.

[weitao, 2014-02-13 18:13:09]

https://codereview.chromium.org/143303007/diff/1/remoting/host/installer/win/...
File remoting/host/installer/win/chromoting.wxs (right):

https://codereview.chromium.org/143303007/diff/1/remoting/host/installer/win/...
remoting/host/installer/win/chromoting.wxs:192: <File
Id="remoting_native_messaging_host.exe"
I prefer to keep the current name. For one, it will be consistent with Linux and
Mac. Besides, I feel that native_messaging_host is too general a term.

On 2014/02/13 01:53:24, Sergey Ulanov wrote:
> maybe call it native_messaging_host.exe? without remoting_ prefix.

https://codereview.chromium.org/143303007/diff/1/remoting/host/pairing_regist...
File remoting/host/pairing_registry_delegate_win.h (right):

https://codereview.chromium.org/143303007/diff/1/remoting/host/pairing_regist...
remoting/host/pairing_registry_delegate_win.h:30: const wchar_t
kPrivilegedKeyName[] = L"secrets";
On 2014/02/13 01:53:24, Sergey Ulanov wrote:
> rename this and kUnprivilegedKeyName to make it clear it's used for pairing
> registry

Done.

https://codereview.chromium.org/143303007/diff/1/remoting/remoting_host.gypi
File remoting/remoting_host.gypi (right):

https://codereview.chromium.org/143303007/diff/1/remoting/remoting_host.gypi#...
remoting/remoting_host.gypi:655:
'host/setup/com.google.chrome.remote_desktop.json.jinja2',
On 2014/02/13 01:53:24, Sergey Ulanov wrote:
> I believe the previous order was correct.

Done.

[weitao, 2014-02-13 18:13:22]

The CQ bit was checked by weitaosu@chromium.org

[commit-bot: I haz the power, 2014-02-13 18:15:18]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/weitaosu@chromium.org/143303007/80001

[commit-bot: I haz the power, 2014-02-13 19:56:24]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/weitaosu@chromium.org/143303007/80001

[commit-bot: I haz the power, 2014-02-13 21:47:46]

Change committed as 251137