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

Should we remove the timestamp field in the manifest header? #671

Open
gtkramer opened this issue Dec 13, 2019 · 1 comment
Open

Should we remove the timestamp field in the manifest header? #671

gtkramer opened this issue Dec 13, 2019 · 1 comment
Labels

Comments

@gtkramer
Copy link

When doing parallel builds and comparing output of mixer in a dev environment to a prod environment, all of the manifests in the Manifest.MoM have different hashes. This is because of the timestamp field in the manifest header.

Is this something we can remove so that debug work is made easier? If I'm not mistaken, when a manifest is signed, that signature has its own timestamp, so maybe we can overlook this value?

@reaganlo reaganlo changed the title Question: Should we remove the timestamp field in the manifest header? Should we remove the timestamp field in the manifest header? Dec 16, 2019
@phmccarty
Copy link
Contributor

There was some discussion about the timestamp field a few years ago. For reference:

clearlinux/swupd-server#83

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

No branches or pull requests

3 participants