diff options
author | benwells <benwells@chromium.org> | 2014-12-22 18:12:27 -0800 |
---|---|---|
committer | Commit bot <commit-bot@chromium.org> | 2014-12-23 02:13:39 +0000 |
commit | 8ffa00af2d4e322e91859c502aa02e0c9b0e1f2a (patch) | |
tree | 399ab692532e1f0ba95da470330286966e2cfeaa /cc/surfaces/surface_aggregator_unittest.cc | |
parent | afe7eaff168a2423855ff6dca1cbab3a95c3f18c (diff) | |
download | chromium_src-8ffa00af2d4e322e91859c502aa02e0c9b0e1f2a.zip chromium_src-8ffa00af2d4e322e91859c502aa02e0c9b0e1f2a.tar.gz chromium_src-8ffa00af2d4e322e91859c502aa02e0c9b0e1f2a.tar.bz2 |
Revert of Clean up Smart Lock cryptohome keys logic: (patchset #5 id:80001 of https://codereview.chromium.org/808563004/)
Reason for revert:
Once this change landed chromeos file manager tests started failing across the MSAN bots.
This is the most likely culprit, so reverting speculatively. If this does not help will reland this change.
See http://build.chromium.org/p/chromium.memory.fyi/builders/Linux%20ChromeOS%20MSan%20Browser%20%282%29/builds/139
Original issue's description:
> Clean up Smart Lock cryptohome keys logic:
>
> 1. Queue all cryptohome keys operations.
> 2. Roll ClearRemoteDevices as a specific case of SetRemoteDevices
> 3. Introduce new RefreshKeys operation using the existing add and remove keys
> operations to replace the current cryptohome keys with new keys.
> 4. After reauthenticating for setup, remove the old cryptohome keys.
>
> BUG=432996
>
> Committed: https://crrev.com/275152c34d8edc5346757288cfffe63444650faa
> Cr-Commit-Position: refs/heads/master@{#309094}
TBR=tbarzic@chromium.org,xiyuan@chromium.org,tengs@chromium.org
NOTREECHECKS=true
NOTRY=true
BUG=432996
Review URL: https://codereview.chromium.org/789793005
Cr-Commit-Position: refs/heads/master@{#309519}
Diffstat (limited to 'cc/surfaces/surface_aggregator_unittest.cc')
0 files changed, 0 insertions, 0 deletions