New issue
Advanced search Search tips

Issue 886953 link

Starred by 0 users

Issue metadata

Status: Started
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Feature

Blocked on:
issue 878440



Sign in to add a comment

verity: move to platform2

Project Member Reported by vapier@chromium.org, Sep 19

Issue description

forking off the platform2 migration request from  issue 878440  (comment #3):

at this point, we have to ask ourselves who the target market for this project ?  do we want to keep it standalone so non-CrOS people can use it ?  do we really think there are that many people out there doing so ?  i'd point out this repo has seen like 3 CLs since 2013, one of which was fixing libc++ compatibility issues, and no outside contributions.  maybe it's a "stable" enough codebase that, for people outside of CrOS, they can just use this old copy.

so if we just accept that no one outside of CrOS cares for updates:
- lets merge this project into platform2
- convert the small amount of C code to C++
- switch from custom utility/library code to libchrome (e.g. all the hashing logic)

outside of the `verity` program, installer/ is the only user of the dm-bht library.  so converting this stuff to C++ shouldn't be a big deal.
 
Sounds good. 

Just an FYI, there are some changes on constructing dm-verity build into update engine in AOSP that we will eventually want in Chrome OS (for DLC probably). so eventually verity project will need more modifications like adding new library functions, etc.

Sign in to add a comment