diff options
| author | sergeyu <sergeyu@chromium.org> | 2016-03-11 23:23:24 -0800 |
|---|---|---|
| committer | Commit bot <commit-bot@chromium.org> | 2016-03-12 07:24:30 +0000 |
| commit | 4357fda5f2518a8dd54121386ba0c3fbe1dc2ec0 (patch) | |
| tree | 402fa355427b8dc0098ae573b5ed715970acd034 /remoting/client | |
| parent | 77ba097ebdbdb049aff2b1459373e35a9fb6a9cb (diff) | |
| download | chromium_src-4357fda5f2518a8dd54121386ba0c3fbe1dc2ec0.zip chromium_src-4357fda5f2518a8dd54121386ba0c3fbe1dc2ec0.tar.gz chromium_src-4357fda5f2518a8dd54121386ba0c3fbe1dc2ec0.tar.bz2 | |
Enable Curve25519 in host and client for PIN-based and third-party auth.
Now client and host can use Spake2Authenticator instead of
V2Authenticator for both PIN-based auth and third-party auth. The plan
is to use cleanup It2Me to use hashed ID, so it will be possible to
remove spake2_plain method completely, so I'm not adding Curve25519
version.
Also pairing authentication needs move work to enable Curve25519 (see
crbug.com/593123), so it's going to be done separately.
Spake2Authenticor implements SPAKE2 over Curve25519, which is defined
in https://tools.ietf.org/html/draft-irtf-cfrg-spake2-03 .
BUG=589698
Review URL: https://codereview.chromium.org/1780403002
Cr-Commit-Position: refs/heads/master@{#380869}
Diffstat (limited to 'remoting/client')
| -rw-r--r-- | remoting/client/chromoting_client.cc | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/remoting/client/chromoting_client.cc b/remoting/client/chromoting_client.cc index 71d020f..7e51042 100644 --- a/remoting/client/chromoting_client.cc +++ b/remoting/client/chromoting_client.cc @@ -215,6 +215,7 @@ void ChromotingClient::StartConnection() { session_manager_->Connect( host_jid_, make_scoped_ptr(new protocol::NegotiatingClientAuthenticator( + signal_strategy_->GetLocalJid(), host_jid_, client_auth_config_))), transport_context_, this); } |