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

Issue 853765 link

Starred by 2 users

Issue metadata

Status: Verified
Owner:
Last visit > 30 days ago
Closed: Jun 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

External builds for some boards still use eCryptFS

Project Member Reported by jayhlee@google.com, Jun 18 2018

Issue description

What steps will reproduce the problem?
(1) build Chromium OS for samus, veyron and cyan boards

What is the expected result?
These newer boards default to and use ext4 user profiles.

What happens instead?
New users always get eCryptFS filesystem. They are prompted to logoff and "install critical update (fs migration wizard) but that never happens on login.

additional information:
Bernie looked into this and it appears that most boards get ext4 because they direncryption flag set in make files. However these boards get it internally because they're marked for ARC++ N. This does not carry over to external though.

Bernie, assigning to you, not sure if fix would be to explicitely set direencryption for these boards or something else.
 

Comment 1 by jayhlee@google.com, Jun 18 2018

Cc: vapier@chromium.org
CC Mike for his input

Thanks for the CL Bernie, what about generic builds? Should we maybe turn this on for them so external projects like CloudReady Neverware get ext4 also?
It looks like the generics already have it.

https://chromium-review.googlesource.com/1077336
Project Member

Comment 3 by bugdroid1@chromium.org, Jun 19 2018

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/board-overlays/+/cd565f2db7e9918ad49169bf53591aff47bd46cd

commit cd565f2db7e9918ad49169bf53591aff47bd46cd
Author: Bernie Thompson <bhthompson@google.com>
Date: Tue Jun 19 04:14:18 2018

Enable direncryption USE flag for samus, cyan, and veyron

These boards get direncryption from the private side of the build, they
should also be set on the public side of the build though. For internal
builds this is a NOP.

BUG= chromium:853765 
TEST=Trybot

Change-Id: I097d64e8a6be7516cf909d75e058c52fd920db15
Reviewed-on: https://chromium-review.googlesource.com/1105117
Commit-Ready: Bernie Thompson <bhthompson@chromium.org>
Tested-by: Bernie Thompson <bhthompson@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>

[modify] https://crrev.com/cd565f2db7e9918ad49169bf53591aff47bd46cd/overlay-cyan/make.conf
[modify] https://crrev.com/cd565f2db7e9918ad49169bf53591aff47bd46cd/overlay-veyron/profiles/base/make.defaults
[modify] https://crrev.com/cd565f2db7e9918ad49169bf53591aff47bd46cd/overlay-samus/profiles/base/make.defaults

Status: Verified (was: Untriaged)

Sign in to add a comment