Issue 688900 link

Starred by 6 users

Issue metadata

Status:	Archived
Owner:	fukino@chromium.org
Closed:	Jun 2017
Cc:	kinaba@chromium.org █ rookrishna@chromium.org sdantul...@chromium.org fukino@chromium.org █ dspaid@chromium.org abod...@chromium.org
Components:	Internals UI>Shell>StartScreen
EstimatedDays:	----
NextAction:	----
OS:	Chrome
Pri:	1
Type:	Bug
M-59 ArcExt4Migration

Blocked on:
issue 590808
issue 688901
issue 699436
issue 699445
issue 699850
issue 702071
issue 702526
issue 703492
issue 704462
issue 706017
issue 706307
issue 711545
issue 713988
issue 714474
issue 714887
issue 714926
issue 714935
issue 715461
issue 715469
issue 716324
issue 719805
issue 720279
issue 721667
issue 731575

Blocking:
issue 347322
issue 675751
issue 711095

eCryptfs -> ext4 encryption migration

Project Member Reported by hashimoto@chromium.org, Feb 6 2017

Issue description

To let existing users use ext4 encryption, we need to implement a tool to migrate existing eCryptfs user directories.

This involves:
- Implement migration logic in cryptohomed.
- Add UI to display the progress of migration.
- Modify chrome's login screen code to start the migration if needed.

Comment 1 by hashimoto@chromium.org, Feb 6 2017

This bug is meant to be the main bug to track the migration work.
Please file a new bug as a blocker of this bug for each sub-task if needed.

Comment 2 by hashimoto@chromium.org, Feb 6 2017

Blockedon: 688901

Comment 3 by uekawa@chromium.org, Feb 6 2017

b/33710917

Comment 4 by uekawa@chromium.org, Feb 7 2017

Owner: fukino@chromium.org

I believe fukino's working on the UI part, so assigning this bug to him.

Comment 5 by dhadd...@chromium.org, Feb 24 2017

Cc: sdantul...@chromium.org abod...@chromium.org rookrishna@chromium.org

Comment 6 by fukino@chromium.org, Mar 8 2017

Labels: M-59
Status: Started (was: Assigned)

Comment 7 by fukino@chromium.org, Mar 8 2017

Components: UI>Shell>StartScreen

Comment 8 by kinaba@chromium.org, Mar 8 2017

Blockedon: 699436

Comment 9 by kinaba@chromium.org, Mar 8 2017

Blockedon: 699445

Comment 10 by kinaba@chromium.org, Mar 9 2017

Blockedon: 699850

Comment 11 by kinaba@chromium.org, Mar 17 2017

Blockedon: 702526

Comment 12 by hashimoto@chromium.org, Mar 23 2017

Blockedon: 704462

Project Member

Comment 13 by bugdroid1@chromium.org, Mar 23 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/platform2/+/8f652d3341b35c7ebcb2b4cd05de9679ccdf54a5

commit 8f652d3341b35c7ebcb2b4cd05de9679ccdf54a5
Author: Kazuhiro Inaba <kinaba@chromium.org>
Date: Thu Mar 23 15:22:34 2017

Revert "cryptohome: Let EnsureCryptohome return an error code, not just a bool."

This reverts commit 4dfe6d299b21c9575faf9551fa602fc85571c556.

Reason for revert: After implementing CL:456671 and CL:458317,
it turned out this generalization was not needed.

BUG= chromium:688900 

Change-Id: I9431d0f2cceb85ea7d1740d5440a4b910fc4be5a
Reviewed-on: https://chromium-review.googlesource.com/458360
Commit-Ready: Kazuhiro Inaba <kinaba@chromium.org>
Tested-by: Kazuhiro Inaba <kinaba@chromium.org>
Reviewed-by: Kazuhiro Inaba <kinaba@chromium.org>

[modify] https://crrev.com/8f652d3341b35c7ebcb2b4cd05de9679ccdf54a5/cryptohome/mount.h
[modify] https://crrev.com/8f652d3341b35c7ebcb2b4cd05de9679ccdf54a5/cryptohome/mount.cc
[modify] https://crrev.com/8f652d3341b35c7ebcb2b4cd05de9679ccdf54a5/cryptohome/mount_unittest.cc