New issue
Advanced search Search tips

Issue 781540 link

Starred by 2 users

Issue metadata

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

Blocked on:
issue 775220



Sign in to add a comment

pack-firmware: Allow skipping models on Signer for which we don't want to sign MP

Project Member Reported by jclinton@chromium.org, Nov 4 2017

Issue description

MP keysets may be out of sync with PreMP keysets for at least two reasons:

* A device was a reference platform and never shipped to customers
* A device is being brought up in a family that has previously shipped but the MP key for the new device hasn't been added to the old MP keyset yet.

This is very tricky because PreMP keys will exist and need to continue to be used.

 
Cc: jclinton@chromium.org

Comment 2 by sjg@chromium.org, Nov 4 2017

Blockedon: 775220
I am working on converting the firmware packer to us cros_config.

Do you think we could just not add instructions if there is no key-id property?
Will that break the current dogfooding flow since those are on pre-MP while the rest of the family will be on MP? I'm not sure how we will handle unrelease devices. Add a new flag to do PreMP keys?


Comment 4 by sjg@chromium.org, Nov 4 2017

I don't know much about this. I suppose adding a flag in the master config is the best idea. Let's try to make it descriptive of what action is taken.

Comment 5 by sjg@chromium.org, Nov 17 2017

Owner: sjg@chromium.org
Status: Started (was: Untriaged)

Comment 6 by sjg@chromium.org, Nov 17 2017

 Issue 786519  has been merged into this issue.

Comment 7 by sjg@chromium.org, Dec 18 2017

Status: Fixed (was: Started)
I think this covers the cases now
Status: Archived (was: Fixed)

Sign in to add a comment