This repository has been archived by the owner on Jan 6, 2023. It is now read-only.
[mixer] Inject Swupd_Root.pem when custom signing #88
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When a user is replacing the signing function of mixer with their own
custom implementation, which implies the
--no-signing
option is beingused, the user is also responsible for injecting the Swupd_Root.pem into
the full chroot. This is required because swupd is hard-coded by
default to look for the update content certificate in
/usr/share/clear/update-ca/Swupd_Root.pem.
Mixer has a not well-documented feature to support adding sideloaded
content that does not come from a package by creating files in the
SERVER_STATE_DIR which the name
<bundle>-extra-files
. Because thecontent certificate is required for swupd, we inject into the
os-core-update bundle.
Closes #85
Signed-off-by: George T Kramer george.t.kramer@intel.com