Block event processing on host/client until the client has authenticated.

remoting/protocol/connection_to_client.h

Index: remoting/protocol/connection_to_client.h
diff --git a/remoting/protocol/connection_to_client.h b/remoting/protocol/connection_to_client.h
index b7aa052c9a298282f093bb4eb8a9b48e39bcf9b7..901a5b185cc8dca0dd7d7762ad09ef68dbc72149 100644
--- a/remoting/protocol/connection_to_client.h
+++ b/remoting/protocol/connection_to_client.h
@@ -72,9 +72,12 @@ class ConnectionToClient :
   // Return pointer to ClientStub.
   virtual ClientStub* client_stub();
 
+  // Record whether the client has been properly authenticated with the host.
+  void SetClientAuthenticated(bool auth);
+
  protected:
   // Protected constructor used by unit test.
-  ConnectionToClient();
+  //ConnectionToClient();

[dmac, 2011/03/04 01:36:27]

should we get rid of this then?

[garykac, 2011/03/04 05:33:24]

oops

 
  private:
   // Callback for protocol Session.
@@ -85,6 +88,11 @@ class ConnectionToClient :
 
   void OnClosed();
 
+  // Initially false, this is set to true once the client has authenticated
+  // properly. When this is false, many client messages (like input events)
+  // will be silently ignored.

[dmac, 2011/03/04 01:36:27]

will they be silently ignored? or will LOGs occur?

[garykac, 2011/03/04 05:33:24]

They should LOG, so I removed "silently"

+  bool client_authenticated_;
+
   // The libjingle channel used to send and receive data from the remote client.
   scoped_refptr<Session> session_;