From 76cfd03fe27318c71804459bf703f7781c3669ef Mon Sep 17 00:00:00 2001 From: "rmsousa@chromium.org" Date: Wed, 3 Apr 2013 10:49:44 +0000 Subject: Separate Client and Host side of NegotiatingAuthenticator, and make the protocol stricter: * Client sends a first message with supported methods (and optionally the first message for a method*). * Host picks a method among those, and sends the first message (or reply). * Client and host are now required to keep using the method selected by the host. Now only the client has the possibility of creating more than one authenticator for the same negotiation (although it's not used now), and, even then, these are two necessarily different authenticators, so there's no chance of NegotiatingAuthenticator having to create the same type of authenticator twice. * I'm keeping this because: (1) we did this before, up to M26, so we have to deal with this case anyway, and (2) it'll be useful for the pinless auth mechanism. BUG=115899 Review URL: https://chromiumcodereview.appspot.com/13368002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@192044 0039d316-1c4b-4281-b951-d872f2087c98 --- remoting/client/plugin/chromoting_instance.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'remoting/client/plugin/chromoting_instance.h') diff --git a/remoting/client/plugin/chromoting_instance.h b/remoting/client/plugin/chromoting_instance.h index e814eaf..a57275a 100644 --- a/remoting/client/plugin/chromoting_instance.h +++ b/remoting/client/plugin/chromoting_instance.h @@ -39,7 +39,7 @@ #include "remoting/protocol/cursor_shape_stub.h" #include "remoting/protocol/input_event_tracker.h" #include "remoting/protocol/mouse_input_filter.h" -#include "remoting/protocol/negotiating_authenticator.h" +#include "remoting/protocol/negotiating_client_authenticator.h" namespace base { class DictionaryValue; -- cgit v1.1