Added pairing with Spake SHA224 key exchange.

Added pairing with Spake SHA224 key exchange.

Pairing generates secret know to the session and
device. The secret will be used for for certificate validation and for device authentication.

BUG=449864
Committed: https://crrev.com/09933be8d731339201df0a9df91bfdaffedd7771
Cr-Commit-Position: refs/heads/master@{#313890}

[Vitaly Buka (NO REVIEWS), 2015-01-26 08:00:04]

vitalybuka@chromium.org changed reviewers:
+ alekseys@chromium.org

[Aleksey Shlyapnikov, 2015-01-26 21:47:46]

lgtm

https://codereview.chromium.org/877613002/diff/40001/chrome/browser/local_dis...
File chrome/browser/local_discovery/privetv3_session.cc (right):

https://codereview.chromium.org/877613002/diff/40001/chrome/browser/local_dis...
chrome/browser/local_discovery/privetv3_session.cc:48: char
kPrivetV3PairingConfirmPath[] = "/privet/v3/pairing/confirm";
Make them all const char.

https://codereview.chromium.org/877613002/diff/40001/chrome/browser/local_dis...
chrome/browser/local_discovery/privetv3_session.cc:82: struct Map {
Element

https://codereview.chromium.org/877613002/diff/40001/chrome/browser/local_dis...
chrome/browser/local_discovery/privetv3_session.cc:244: bool
has_compartible_crypto = false;
has_compatible_crypto

https://codereview.chromium.org/877613002/diff/40001/chrome/browser/local_dis...
File chrome/browser/local_discovery/privetv3_setup_flow.cc (right):

https://codereview.chromium.org/877613002/diff/40001/chrome/browser/local_dis...
chrome/browser/local_discovery/privetv3_setup_flow.cc:91:
PrivetV3Session::PairingType::PAIRING_TYPE_EMBEDDEDCODE)) {
std::count will iterate over all elements, use std::find.

[Vitaly Buka (NO REVIEWS), 2015-01-26 23:14:34]

vitalybuka@chromium.org changed reviewers:
+ mednik@chromium.org, zentaro@chromium.org

[Vitaly Buka (NO REVIEWS), 2015-01-26 23:17:51]

On 2015/01/26 23:14:34, Vitaly Buka wrote:

Zen, Max this change will break compatibility with py simulator.
Do you want me to update simulator, or I can do that later after all Chrome
changes landed.

[Vitaly Buka (NO REVIEWS), 2015-01-27 00:16:33]

https://codereview.chromium.org/877613002/diff/40001/chrome/browser/local_dis...
File chrome/browser/local_discovery/privetv3_session.cc (right):

https://codereview.chromium.org/877613002/diff/40001/chrome/browser/local_dis...
chrome/browser/local_discovery/privetv3_session.cc:48: char
kPrivetV3PairingConfirmPath[] = "/privet/v3/pairing/confirm";
On 2015/01/26 21:47:45, Aleksey Shlyapnikov wrote:
> Make them all const char.

Done.

https://codereview.chromium.org/877613002/diff/40001/chrome/browser/local_dis...
chrome/browser/local_discovery/privetv3_session.cc:82: struct Map {
On 2015/01/26 21:47:45, Aleksey Shlyapnikov wrote:
> Element

Done.

https://codereview.chromium.org/877613002/diff/40001/chrome/browser/local_dis...
chrome/browser/local_discovery/privetv3_session.cc:244: bool
has_compartible_crypto = false;
On 2015/01/26 21:47:45, Aleksey Shlyapnikov wrote:
> has_compatible_crypto

Done.

[mednik, 2015-01-27 04:34:06]

On 2015/01/26 23:17:51, Vitaly Buka wrote:
> On 2015/01/26 23:14:34, Vitaly Buka wrote:
> 
> Zen, Max this change will break compatibility with py simulator.
> Do you want me to update simulator, or I can do that later after all Chrome
> changes landed.

I have no problem with you updating the simulator right after all Chrome changes
land. Can you prepare the simulator CL at roughly the same time so there isn't a
long delay? You can also land the Chrome changes once the simulator CL is ready
to be landed shortly thereafter too.

Do you have a sense for how many more Chrome changes will be required when you
say "all Chrome changes"?

[Vitaly Buka (NO REVIEWS), 2015-01-27 17:33:57]

On 2015/01/27 04:34:06, mednik wrote:
> On 2015/01/26 23:17:51, Vitaly Buka wrote:
> > On 2015/01/26 23:14:34, Vitaly Buka wrote:
> > 
> > Zen, Max this change will break compatibility with py simulator.
> > Do you want me to update simulator, or I can do that later after all Chrome
> > changes landed.
> 
> I have no problem with you updating the simulator right after all Chrome
changes
> land. Can you prepare the simulator CL at roughly the same time so there isn't
a
> long delay? You can also land the Chrome changes once the simulator CL is
ready
> to be landed shortly thereafter too.
> 
> Do you have a sense for how many more Chrome changes will be required when you
> say "all Chrome changes"?

Should be just authentication after pairing.
I'll consider to update simulator before landing both.

[Aleksey Shlyapnikov, 2015-01-27 23:20:15]

lgtm

[Vitaly Buka (NO REVIEWS), 2015-01-29 18:08:45]

The CQ bit was checked by vitalybuka@chromium.org

[commit-bot: I haz the power, 2015-01-29 18:09:13]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/877613002/160001

[commit-bot: I haz the power, 2015-01-29 18:40:48]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2015-01-29 18:40:48]

Try jobs failed on following builders:
  win_gpu on tryserver.chromium.gpu
(http://build.chromium.org/p/tryserver.chromium.gpu/builders/win_gpu/builds/11...)

[Vitaly Buka (NO REVIEWS), 2015-01-29 18:44:43]

The CQ bit was checked by vitalybuka@chromium.org

[commit-bot: I haz the power, 2015-01-29 18:45:45]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/877613002/180001

[Vitaly Buka (NO REVIEWS), 2015-01-29 18:46:43]

The CQ bit was unchecked by vitalybuka@chromium.org

[Vitaly Buka (NO REVIEWS), 2015-01-29 18:47:00]

The CQ bit was checked by vitalybuka@chromium.org

[commit-bot: I haz the power, 2015-01-29 18:47:17]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/877613002/200001

[commit-bot: I haz the power, 2015-01-29 19:21:21]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2015-01-29 19:21:22]

Try jobs failed on following builders:
  win_chromium_x64_rel_ng on tryserver.chromium.win
(http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_x64_...)

[Vitaly Buka (NO REVIEWS), 2015-01-29 23:57:49]

The CQ bit was checked by vitalybuka@chromium.org

[commit-bot: I haz the power, 2015-01-29 23:59:14]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/877613002/220001

[commit-bot: I haz the power, 2015-01-30 00:57:01]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2015-01-30 00:57:02]

Try jobs failed on following builders:
  linux_chromium_chromeos_rel_ng on tryserver.chromium.linux
(http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[Vitaly Buka (NO REVIEWS), 2015-01-30 06:05:29]

The CQ bit was checked by vitalybuka@chromium.org

[commit-bot: I haz the power, 2015-01-30 06:05:46]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/877613002/240001

[commit-bot: I haz the power, 2015-01-30 07:24:29]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2015-01-30 07:24:30]

Try jobs failed on following builders:
  mac_chromium_rel_ng on tryserver.chromium.mac
(http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_...)

[Vitaly Buka (NO REVIEWS), 2015-01-30 07:45:40]

The CQ bit was checked by vitalybuka@chromium.org

[commit-bot: I haz the power, 2015-01-30 07:46:30]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/877613002/260001

[commit-bot: I haz the power, 2015-01-30 09:37:48]

Committed patchset #14 (id:260001)

[commit-bot: I haz the power, 2015-01-30 09:39:13]

Patchset 14 (id:??) landed as
https://crrev.com/09933be8d731339201df0a9df91bfdaffedd7771
Cr-Commit-Position: refs/heads/master@{#313890}