PART4: Removed the owner cache special handling from UserCrosSettingsProvider.

chrome/browser/chromeos/login/signed_settings.cc

Index: chrome/browser/chromeos/login/signed_settings.cc
diff --git a/chrome/browser/chromeos/login/signed_settings.cc b/chrome/browser/chromeos/login/signed_settings.cc
index 1ba9b8497b56e213780e5c8b029b71d19b68d08d..0b41d04fe40f6be9c2b41402da3b6aa21b75c464 100644
--- a/chrome/browser/chromeos/login/signed_settings.cc
+++ b/chrome/browser/chromeos/login/signed_settings.cc
@@ -363,6 +363,8 @@ void StorePropertyOp::SetInPolicy(const std::string& prop,
       if ((*i)->GetAsString(&email))
         whitelist_proto->add_user_whitelist(email.c_str());
     }
+  } else if (prop == kDeviceOwner) {
+    // We don't serialize this one to the policy blob.

[Mattias Nissler (ping if slow), 2011/10/07 13:46:52]

It's actually good to make it a NOTREACHED(), do you know why we had this branch
before?

[pastarmovj, 2011/10/13 12:00:41]

Actually it is not NOTREACHED() it will be called whenever the user calls
CrosSettings.Set(kDeviceOwner, new_powner); which will put it in the local_state
cache it should however not be serialized down to the blob as this is not the
way to set the owner. 
The session_manager does that for us. Actually the cool thing now is that once
the session_manager writes its version of the owner we'll update the cache with
that and thus there is no way that a user can try to trick the browser into
thinking another user is the owner because this will be overwritten on policy
load. 
We don't trust this value for nothing but UI though so not really a security
issue.

   } else {
     NOTREACHED();
   }