Skip to content
This repository has been archived by the owner on Jan 6, 2023. It is now read-only.

Sign latest and first files when sign_update is defined #98

Open
gtkramer opened this issue Dec 20, 2019 · 3 comments
Open

Sign latest and first files when sign_update is defined #98

gtkramer opened this issue Dec 20, 2019 · 3 comments
Labels
effort 1 Low level of effort required RFC Request for Comments
Milestone

Comments

@gtkramer
Copy link
Contributor

When using the --no-signing option on mixer, mixer will not sign the latest file. This is not being done today by our process and is required for supporting future enhancements to swupd. The first file is not used by mixer or swupd, but supports creating delta packs from the first build in every format, and also supports MCA. This file should also be signed.

@gtkramer gtkramer added this to the Pairity milestone Dec 20, 2019
@gtkramer gtkramer added the effort 1 Low level of effort required label Dec 20, 2019
@gtkramer
Copy link
Contributor Author

This finishes the last bit of implementing custom signing

@gtkramer gtkramer added the RFC Request for Comments label Dec 20, 2019
@gtkramer
Copy link
Contributor Author

gtkramer commented Dec 20, 2019

I'm not sure if the first file needs signed? It's a DevOps-only artifacts that is useful for us to keep track of producing delta packs from the first build in the format to the current as an optimization for swupd clients. It's neither produced by mixer nor consumed by swupd, but is helpful for MCA according to @jwakre

@mbelluzzo
Copy link
Contributor

We do have an equivalent file now under update that is used by swupd and signed by mixer already. So nowadays it is possible to stop using the root latest file in favour of the update/ one.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
effort 1 Low level of effort required RFC Request for Comments
Projects
None yet
Development

No branches or pull requests

2 participants