diff options
| author | cmasone@chromium.org <cmasone@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-04-15 23:14:37 +0000 |
|---|---|---|
| committer | cmasone@chromium.org <cmasone@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-04-15 23:14:37 +0000 |
| commit | 45636929754cf2622508668cdeded4f14196af81 (patch) | |
| tree | b835e1d94ba7a85c386f71e6a23a6510740a9431 /DEPS | |
| parent | 5ce82f432ac5cd5f241eb3a6b549c6e8089c3641 (diff) | |
| download | chromium_src-45636929754cf2622508668cdeded4f14196af81.zip chromium_src-45636929754cf2622508668cdeded4f14196af81.tar.gz chromium_src-45636929754cf2622508668cdeded4f14196af81.tar.bz2 | |
[Chrome OS] Reimplement SignedSettings in terms of device policies.
Owner settings are being re-implemented as a single, signed protobuf
that is stored by the chromium os session_manager. Thus, to write a
setting, you need to have the existing policy, update it, re-sign it,
and then have it stored. This could be done by requesting the policy
every time, or by caching it and updating it upon every successful
store. We cache it in the OwnershipService singleton. The SignedSettings
API remains unchanged, semantically.
This should all be re-implemented more cleanly (remove the out-dated notions
of storing/retrieving properties and whitelisting, etc) as part of
http://crosbug.com/14054
BUG=chromium-os:13230
TEST=unit tests
Review URL: http://codereview.chromium.org/6831011
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@81828 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'DEPS')
0 files changed, 0 insertions, 0 deletions