Protocol-level changes required to support PIN-less authentication.

remoting/proto/control.proto

Index: remoting/proto/control.proto
diff --git a/remoting/proto/control.proto b/remoting/proto/control.proto
index 88eda00f68fd8c9c0e5d93dd45436d8847417cbc..a7489fb1b88b792b31966b6b09bc582a38c9c9af 100644
--- a/remoting/proto/control.proto
+++ b/remoting/proto/control.proto
@@ -53,3 +53,16 @@ message Capabilities {
   // are separated by spaces).
   optional string capabilities = 1;
 }
+
+message PairingRequest {
+  // Human-readable name of the client.
+  optional string client_name = 1;
+}
+
+message PairingReply {

[rmsousa, 2013/05/09 03:55:02]

nit: We typically use Request/Response for proto rpc messages. Even though we're
not using Protobuf's rpc facility, these are following similar semantics, so I
think we should keep the naming scheme.
https://developers.google.com/protocol-buffers/docs/style

[Jamie, 2013/05/09 17:59:52]

Done.

+  // Unique identifier for this client.
+  optional string client_id = 1;
+
+  // Shared secret for this client.
+  optional string shared_secret = 2;
+}