[EasyUnlock] Serialize and store BeaconSeeds along as cryptohome key metadata.

chrome/browser/chromeos/login/easy_unlock/easy_unlock_types.cc

Index: chrome/browser/chromeos/login/easy_unlock/easy_unlock_types.cc
diff --git a/chrome/browser/chromeos/login/easy_unlock/easy_unlock_types.cc b/chrome/browser/chromeos/login/easy_unlock/easy_unlock_types.cc
index d955330655941212c323323de34f497afe139a74..f5bc8898736cd97931c420a5fad7305b546475c5 100644
--- a/chrome/browser/chromeos/login/easy_unlock/easy_unlock_types.cc
+++ b/chrome/browser/chromeos/login/easy_unlock/easy_unlock_types.cc
@@ -12,6 +12,7 @@ const char kEasyUnlockKeyMetaNamePsk[] = "eu.psk";
 const char kEasyUnlockKeyMetaNamePubKey[] = "eu.pubkey";
 const char kEasyUnlockKeyMetaNameChallenge[] = "eu.C";
 const char kEasyUnlockKeyMetaNameWrappedSecret[] = "eu.WUK";
+const char kEasyUnlockKeyMetaNameSerializedBeaconSeeds[] = "eu.BS";

[Ryan Hansberry, 2017/05/09 02:44:08]

I don't know much about how this is stored, but these names are really short --
is there any danger of collision with constants elsewhere in Chrome?

[Tim Song, 2017/05/10 18:23:26]

These names are prefixed with "eu" (EasyUnlock), so there shouldn't be any
collisions if other projects doing use the same prefix.

 
 EasyUnlockDeviceKeyData::EasyUnlockDeviceKeyData()
     : bluetooth_type(BLUETOOTH_CLASSIC) {}