Add gnubby authentication to remoting host

chrome/browser/policy/configuration_policy_handler_list_factory.cc

Index: chrome/browser/policy/configuration_policy_handler_list_factory.cc
diff --git a/chrome/browser/policy/configuration_policy_handler_list_factory.cc b/chrome/browser/policy/configuration_policy_handler_list_factory.cc
index ea5aa6dfcb12769c58f31ee20e6b95baddc36c9f..d9e4e03cb4208956ba56420f560ceac12fe26de7 100644
--- a/chrome/browser/policy/configuration_policy_handler_list_factory.cc
+++ b/chrome/browser/policy/configuration_policy_handler_list_factory.cc
@@ -265,6 +265,9 @@ const PolicyToPreferenceMapEntry kSimplePolicyMap[] = {
   { key::kRemoteAccessHostAllowClientPairing,
     prefs::kRemoteAccessHostAllowClientPairing,
     base::Value::TYPE_BOOLEAN },
+  { key::kRemoteAccessHostAllowGnubbyAuth,

[Sergey Ulanov, 2014/01/25 02:03:33]

I don't think you need this. Chromoting host doesn't rely on policy code from
chrome (instead it uses remoting/host/policy_hack). We only share policy
templates.

[psj, 2014/01/29 09:07:15]

I added it because other remoting policies are named here. I can definitely
remove it, though, if it really isn't needed.

+    prefs::kRemoteAccessHostAllowGnubbyAuth,
+    base::Value::TYPE_BOOLEAN },
   { key::kCloudPrintProxyEnabled,
     prefs::kCloudPrintProxyEnabled,
     base::Value::TYPE_BOOLEAN },