New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 704462 link

Starred by 2 users

Issue metadata

Status: Archived
Owner:
Closed: Mar 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug

Blocking:
issue 688900



Sign in to add a comment

Add an easy way to create a new user home directory with eCryptfs

Project Member Reported by hashimoto@chromium.org, Mar 23 2017

Issue description

Currently, to disable ext4 ecrypto to create a new user home directory with eCryptfs, developers have to manually edit /etc/init/cryptohomed.conf to remove --direncryption command line option, and reboot the system.

We have to add a more convenient way to do the same thing to make development and testing easy.
 
Project Member

Comment 1 by bugdroid1@chromium.org, Mar 25 2017

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

commit 833fe8c81989ca08a045847285169c31b1b4f53c
Author: Ryo Hashimoto <hashimoto@google.com>
Date: Sat Mar 25 02:38:02 2017

cryptohome: Add a new CreateRequest param for eCryptfs migration testing

force_ecryptfs is added to CreateRequest.
cryptohome command line tool supports --ecryptfs option.

BUG= chromium:704462 
TEST=cryptohome --action=mount_ex --user=foo@example.com --password=foo --key_label=foo --create --ecryptfs
TEST=cros_workon_make --board=reef cryptohome --test
CQ-DEPEND=CL:458361

Change-Id: I422a522645585846fea0c2b8ff378fdd9440a330
Reviewed-on: https://chromium-review.googlesource.com/458467
Commit-Ready: Ryo Hashimoto <hashimoto@chromium.org>
Tested-by: Ryo Hashimoto <hashimoto@chromium.org>
Reviewed-by: Kazuhiro Inaba <kinaba@chromium.org>
Reviewed-by: Andrey Pronin <apronin@chromium.org>

[modify] https://crrev.com/833fe8c81989ca08a045847285169c31b1b4f53c/cryptohome/cryptohome.cc
[modify] https://crrev.com/833fe8c81989ca08a045847285169c31b1b4f53c/cryptohome/service.cc

Project Member

Comment 2 by bugdroid1@chromium.org, Mar 25 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/platform/system_api/+/6d2fe8b135a297e2df3b61a122bcf5b611573d3c

commit 6d2fe8b135a297e2df3b61a122bcf5b611573d3c
Author: Ryo Hashimoto <hashimoto@google.com>
Date: Sat Mar 25 02:38:02 2017

cryptohome: Add a new CreateRequest param for eCryptfs migration testing

force_ecryptfs is added to CreateRequest.
cryptohome command line tool supports --ecryptfs option.

BUG= chromium:704462 
TEST=cryptohome --action=mount_ex --user=foo@example.com --password=foo
--key_label=foo --create --ecryptfs

Change-Id: Ia8ebc40dcd75524ffda629828b9d58464daf3413
Reviewed-on: https://chromium-review.googlesource.com/458361
Commit-Ready: Ryo Hashimoto <hashimoto@chromium.org>
Tested-by: Ryo Hashimoto <hashimoto@chromium.org>
Reviewed-by: Kazuhiro Inaba <kinaba@chromium.org>
Reviewed-by: Andrey Pronin <apronin@chromium.org>

[modify] https://crrev.com/6d2fe8b135a297e2df3b61a122bcf5b611573d3c/dbus/cryptohome/rpc.proto

Status: Fixed (was: Started)
Now the command line tool is ready.

How to create a new user with eCryptfs.
 1. Press Ctrl+Alt+F2 to enter VT2.
 2. As root, cryptohome --action=mount_ex --user=<user email> --key_label=foo --create --ecryptfs
 3. Back to the Chrome UI, click "Add person" to add the same user.

#3 results in creating a new Chrome profile with the eCryptfs home directory created in #2.

How to confirm the profile is running with eCryptfs home directory:
 1. Press Ctrl+Alt+T to enter crosh
 2. Run cryptohome_status
 3. In the output JSON, mounts->type is "ecryptfs" instead of "dircrypto".
Correction to #3:

How to create a new user with eCryptfs.
 1. Press Ctrl+Alt+F2 to enter VT2.
 2a. As root, cryptohome --action=mount_ex --user=<user email> --key_label=foo --create --ecryptfs
 2b. Unmount the newly created user directory with cryptohome --action=unmount --user=<user email>
 3. Back to the Chrome UI, click "Add person" to add the same user.

Comment 5 by dchan@google.com, May 30 2017

Labels: VerifyIn-60

Comment 6 by dchan@chromium.org, Aug 1 2017

Labels: VerifyIn-61

Comment 7 by dchan@chromium.org, Jan 22 2018

Status: Archived (was: Fixed)

Sign in to add a comment