Postpone loading about:flags ui until the certificates have been loaded

chrome/browser/chromeos/login/parallel_authenticator.cc

Index: chrome/browser/chromeos/login/parallel_authenticator.cc
diff --git a/chrome/browser/chromeos/login/parallel_authenticator.cc b/chrome/browser/chromeos/login/parallel_authenticator.cc
index 44aef966a9e5afce6873b8c6bf10b9db1e20d8ca..8891c4ec49ae5a39d4e4d93678877adb32a775a5 100644
--- a/chrome/browser/chromeos/login/parallel_authenticator.cc
+++ b/chrome/browser/chromeos/login/parallel_authenticator.cc
@@ -457,10 +457,11 @@ bool ParallelAuthenticator::VerifyOwner() {
 }
 
 void ParallelAuthenticator::OnOwnershipChecked(
-    DeviceSettingsService::OwnershipStatus status,
-    bool is_owner) {
+    DeviceSettingsService::OwnershipStatus status) {
   // Now we can check if this user is the owner.
-  user_can_login_ = is_owner;
+  // TODO(tbarzic): This is broken. At this point, DeviceSettingsService will

[pastarmovj, 2013/09/05 12:48:18]

This used to be the case before though - the owner key was loaded as part of the
login procedure and could be verified here. This is what has regressed policy
recovery too. :-(

[tbarzic, 2013/09/05 17:59:17]

yep. I know..
that reminds me, I forgot to put a bug # in the comment..

+  // never have private key loaded.
+  user_can_login_ = DeviceSettingsService::Get()->HasPrivateOwnerKey();
   owner_is_verified_ = true;
   Resolve();
 }