Policy implementation for encryptfs to ext4 migration strategy

Policy implementation for encryptfs to ext4 migration strategy

Chrome OS encrypts each user’s data with the user’s password. With M60,
Chrome OS is switching from ecryptfs to ext4 encryption. ARC N requires
ext4 encryption. The policy DeviceEcryptfsMigrationStrategy states
whether the device is allowed to use ARC or not. If it's not allowed,
the process of data migration should not be launched.

Design doc: https://docs.google.com/document/d/18Nz2OClU6CDb7TpZ2MbO4yySvgiOYWsFUxrR4LQYzXU/edit?ts=5915e354#

This implementation is planned to become obsolete, and be rolled back
after the migration process will finish. The issue for that:
http://crbug.com/725493

BUG=722371
TEST=Manual tests and unit tests.

Review-Url: https://codereview.chromium.org/2890843002
Cr-Original-Commit-Position: refs/heads/master@{#481499}
Review-Url: https://codereview.chromium.org/2956633002 .
Cr-Commit-Position: refs/branch-heads/3112@{#448}
Cr-Branched-From: b6460e24cf59f429d69de255538d0fc7a425ccf9-refs/heads/master@{#474897}
Committed: https://chromium.googlesource.com/chromium/src/+/f3deed295ff4ee4d8e0a42a4d9bb19d528dd2d2e

[igorcov, 2017-06-23 11:19:57]

Description was changed from

==========
Policy implementation for encryptfs to ext4 migration strategy

Chrome OS encrypts each user’s data with the user’s password. With M60,
Chrome OS is switching from ecryptfs to ext4 encryption. ARC N requires
ext4 encryption. The policy DeviceEcryptfsMigrationStrategy states
whether the device is allowed to use ARC or not. If it's not allowed,
the process of data migration should not be launched.

Design doc:
https://docs.google.com/document/d/18Nz2OClU6CDb7TpZ2MbO4yySvgiOYWsFUxrR4LQYz...

This implementation is planned to become obsolete, and be rolled back
after the migration process will finish. The issue for that:
http://crbug.com/725493

BUG=722371
TEST=Manual tests and unit tests.

Review-Url: https://codereview.chromium.org/2890843002
Cr-Commit-Position: refs/heads/master@{#481499}
(cherry picked from commit 24be4caf84c7c14e68c4c10206c3ea0a506c0ee6)
==========

to

==========
Policy implementation for encryptfs to ext4 migration strategy

Chrome OS encrypts each user’s data with the user’s password. With M60,
Chrome OS is switching from ecryptfs to ext4 encryption. ARC N requires
ext4 encryption. The policy DeviceEcryptfsMigrationStrategy states
whether the device is allowed to use ARC or not. If it's not allowed,
the process of data migration should not be launched.

Design doc:
https://docs.google.com/document/d/18Nz2OClU6CDb7TpZ2MbO4yySvgiOYWsFUxrR4LQYz...

This implementation is planned to become obsolete, and be rolled back
after the migration process will finish. The issue for that:
http://crbug.com/725493

BUG=722371
TEST=Manual tests and unit tests.

Review-Url: https://codereview.chromium.org/2890843002
Cr-Original-Commit-Position: refs/heads/master@{#481499}
Review-Url: https://codereview.chromium.org/2956633002 .
Cr-Commit-Position: refs/branch-heads/3112@{#448}
Cr-Branched-From:
b6460e24cf59f429d69de255538d0fc7a425ccf9-refs/heads/master@{#474897}
Committed:
https://chromium.googlesource.com/chromium/src/+/f3deed295ff4ee4d8e0a42a4d9bb...
==========

[igorcov, 2017-06-23 11:19:59]

Committed patchset #1 (id:1) manually as
f3deed295ff4ee4d8e0a42a4d9bb19d528dd2d2e.