Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support firmware UUID generation #86

Closed
fhunleth opened this issue Jun 8, 2018 · 1 comment
Closed

Support firmware UUID generation #86

fhunleth opened this issue Jun 8, 2018 · 1 comment

Comments

@fhunleth
Copy link
Collaborator

fhunleth commented Jun 8, 2018

Problem:

The version number field is not trusted to unambiguously represent the firmware that's running on a device. The vcs_identifier can be used, but isn't guaranteed to be populated. The solution of running a SHA-256 over the .fw file after it has been generated is not desirable since things like signing .fw files would change the computed hash but not alter the contents.

Proposed solution:

Add a virtual meta-uuid field that can be deterministically calculated based on the contents of the .fw file. This could be based on the meta.conf file since that file contains hashes of all of the constituent files. If meta-uuid is calculated rather than stored, it will work on .fw files created with older versions of fwup.

@fhunleth
Copy link
Collaborator Author

This is partially supported by v1.2.0. You can see the UUID by dumping the .fw file's metadata using fwup -m. Storage of the firmware UUID on the target can't be automated using only fwup and additions to the fwup.conf, though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant