-
Notifications
You must be signed in to change notification settings - Fork 12
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
Publish / make use of .buildinfo
files for RPM packages
#418
Comments
cfm
added a commit
to freedomofpress/securedrop-yum-prod
that referenced
this issue
Feb 27, 2025
This is a step towards automating the check of pre-signature reproducibility proposed by freedomofpress/securedrop-builder#418.
cfm
added a commit
to freedomofpress/securedrop-yum-prod
that referenced
this issue
Feb 27, 2025
This is a step towards automating the check of pre-signature reproducibility proposed by freedomofpress/securedrop-builder#418.
cfm
added a commit
to freedomofpress/securedrop-yum-prod
that referenced
this issue
Feb 27, 2025
This is a step towards automating the check of pre-signature reproducibility proposed by freedomofpress/securedrop-builder#418.
cfm
added a commit
to freedomofpress/securedrop-yum-prod
that referenced
this issue
Feb 27, 2025
This is a step towards automating the check of pre-signature reproducibility proposed by freedomofpress/securedrop-builder#418.
cfm
added a commit
to freedomofpress/securedrop-yum-prod
that referenced
this issue
Feb 28, 2025
This is a step towards automating the check of pre-signature reproducibility proposed by freedomofpress/securedrop-builder#418.
cfm
added a commit
to freedomofpress/securedrop-yum-prod
that referenced
this issue
Feb 28, 2025
This is a step towards automating the check of pre-signature reproducibility proposed by freedomofpress/securedrop-builder#418.
cfm
added a commit
to freedomofpress/securedrop-yum-prod
that referenced
this issue
Feb 28, 2025
This is a step towards automating the check of pre-signature reproducibility proposed by freedomofpress/securedrop-builder#418.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Adding this here as it would apply to
securedrop-updater
as well assecuredrop-workstation
I just noticed that QubesOS publishes
.buildinfo
files for RPM packages (example), and it turns out they use a relatively simple script for this. They also have a tool to verify reproducibility that take these files as input.I think following their example here would be cool, though it would require us to switch up how we build RPM packages right now (adding a step to create SRPMs).
The text was updated successfully, but these errors were encountered: