Add gnubby authentication to remoting host

components/policy/resources/policy_templates.json

Index: components/policy/resources/policy_templates.json
diff --git a/components/policy/resources/policy_templates.json b/components/policy/resources/policy_templates.json
index 37bca321ee4f33ad8c17e8e07d1030560c5881fc..a4ae3366299a5141cca8c3f9e5e5b23f6ed66b83 100644
--- a/components/policy/resources/policy_templates.json
+++ b/components/policy/resources/policy_templates.json
@@ -118,7 +118,7 @@
 #   persistent IDs for all fields (but not for groups!) are needed. These are
 #   specified by the 'id' keys of each policy. NEVER CHANGE EXISTING IDs,
 #   because doing so would break the deployed wire format!
-#   For your editing convenience: highest ID currently used: 253
+#   For your editing convenience: highest ID currently used: 254
 #
 # Placeholders:
 #   The following placeholder strings are automatically substituted:
@@ -625,6 +625,22 @@
 
           If this setting is disabled, then this feature will not be available.''',
         },
+        {
+          'name': 'RemoteAccessHostAllowGnubbyAuth',
+          'type': 'main',
+          'schema': { 'type': 'boolean' },
+          'supported_on': ['chrome.*:30-'],

[dconnelly, 2014/01/29 09:21:08]

Update the supported_on field to whichever Chrome release you're targeting.

[psj, 2014/02/04 23:43:56]

Done.

+          'features': {
+            'dynamic_refresh': True,
+            'per_profile': False,
+          },
+          'example_value': True,
+          'id': 254,
+          'caption': '''Allow gnubby authentication''',
+          'desc': '''If this setting is enabled, then gnubby authentication requests will be proxied across a remote host connection.
+
+          If this setting is disabled or not configured, gnubby authentication requests will not be proxied.''',
+        },
       ],
     },
     {