New issue
Advanced search Search tips

Issue 682131 link

Starred by 2 users

Issue metadata

Status: Archived
Owner:
Closed: Feb 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug

Blocking:
issue 347322



Sign in to add a comment

cryptohome --action=status should report the encryption type

Project Member Reported by hashimoto@chromium.org, Jan 18 2017

Issue description

After introducing ext4 crypto, a user's cryptohome can be either ext4 crypto or ecryptfs.
We should let Mount::GetStatus() report the encryption type so that the info will be included in cryptohome --aciton=status output.
 
Status: Started (was: Available)
Project Member

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

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

commit b512539f9d32b03a9bd2b543478d5c5db6f954bf
Author: Ryo Hashimoto <hashimoto@google.com>
Date: Sat Feb 25 12:19:52 2017

cryptohome: Report mount type

Let cryptohome --action=status report the mount type.

BUG= chromium:682131 
TEST=cryptohome --action=status

Change-Id: Ia49b609975817ca08ee3f58f62830c5e1eb5996a
Reviewed-on: https://chromium-review.googlesource.com/446296
Commit-Ready: Ryo Hashimoto <hashimoto@chromium.org>
Tested-by: Ryo Hashimoto <hashimoto@chromium.org>
Reviewed-by: Ryo Hashimoto <hashimoto@chromium.org>

[modify] https://crrev.com/b512539f9d32b03a9bd2b543478d5c5db6f954bf/cryptohome/mount.h
[modify] https://crrev.com/b512539f9d32b03a9bd2b543478d5c5db6f954bf/cryptohome/mount.cc

Status: Fixed (was: Started)

Comment 4 by dchan@google.com, Apr 17 2017

Labels: VerifyIn-59

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, Oct 14 2017

Status: Archived (was: Fixed)

Sign in to add a comment