[Sync] Implement keystore migration support.

We'll now trigger migration if the keystore key is available, the cryptographer
is ready, and the nigori node isn't already properly migrated. Note that this
means we won't trigger migration without at least the implicit gaia password
already available to the cryptographer, in order to support backwards
compatibility with older clients. Eventually that will change.

In addition, once a nigori node has been migrated, any client that supports
keystore encryption will follow the new encryption constraints, whether
or not the --sync-keystore-encryption flag is passed. This means that if
the user sets a custom passphrase, encrypt everything will also be enabled
(and vice versa).

Migration-aware conflict resolution is not implemented yet.

BUG=129665


Review URL: https://chromiumcodereview.appspot.com/10916036

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@156646 0039d316-1c4b-4281-b951-d872f2087c98

1 files changed, 3 insertions, 3 deletions

diff --git a/sync/internal_api/public/util/sync_string_conversions.cc b/sync/internal_api/public/util/sync_string_conversions.cc
index fec2720..495fadf 100644
--- a/sync/internal_api/public/util/sync_string_conversions.cc
+++ b/sync/internal_api/public/util/sync_string_conversions.cc
@@ -32,15 +32,15 @@ const char* PassphraseRequiredReasonToString(
   }
 }
 
-const char* PassphraseStateToString(PassphraseState state) {
-  switch (state) {
+const char* PassphraseTypeToString(PassphraseType type) {
+  switch (type) {
     ENUM_CASE(IMPLICIT_PASSPHRASE);
     ENUM_CASE(KEYSTORE_PASSPHRASE);
     ENUM_CASE(FROZEN_IMPLICIT_PASSPHRASE);
     ENUM_CASE(CUSTOM_PASSPHRASE);
     default:
       NOTREACHED();
-      return "INVALID_PASSPHRASE_STATE";
+      return "INVALID_PASSPHRASE_TYPE";
   }
 }