Add gnubby authentication to remoting host

remoting/remoting.gyp

Index: remoting/remoting.gyp
diff --git a/remoting/remoting.gyp b/remoting/remoting.gyp
index 23d400e08a0b88e8cf5e7d17521985e64aefccd5..3f9bc64459974118f57ae96b9ca958f119942645 100644
--- a/remoting/remoting.gyp
+++ b/remoting/remoting.gyp
@@ -341,6 +341,14 @@
             'host/disconnect_window_win.cc',
             'host/dns_blackhole_checker.cc',
             'host/dns_blackhole_checker.h',
+            'host/gnubby_advertiser.cc',
+            'host/gnubby_advertiser.h',
+            'host/gnubby_auth_handler.cc',
+            'host/gnubby_auth_handler.h',
+            'host/gnubby_connection.cc',
+            'host/gnubby_connection.h',
+            'host/gnubby_connection_factory.cc',
+            'host/gnubby_connection_factory.h',
             'host/heartbeat_sender.cc',
             'host/heartbeat_sender.h',
             'host/host_change_notification_listener.cc',
@@ -2605,6 +2613,12 @@
         'host/desktop_shape_tracker_unittest.cc',
         'host/desktop_session_agent.cc',
         'host/desktop_session_agent.h',
+        'host/gnubby_auth_handler.cc',

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

you do not need to duplicate these files here. remoting_unittest already depends
on remoting_host target which builds these files. (I have a pending CL that
removes the other non-test files above:
https://codereview.chromium.org/145003019/)

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

Hmm, I was getting unresolved link errors before I added those, but it seems to
be working fine now...

+        'host/gnubby_auth_handler_unittest.cc',
+        'host/gnubby_advertiser.cc',
+        'host/gnubby_advertiser_unittest.cc',
+        'host/gnubby_connection.cc',
+        'host/gnubby_connection_unittest.cc',
         'host/heartbeat_sender_unittest.cc',
         'host/host_status_sender_unittest.cc',
         'host/host_change_notification_listener_unittest.cc',