-
Notifications
You must be signed in to change notification settings - Fork 305
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
Last signature wins in ostree summary -u
#1488
Comments
jeremy-hiatt
added a commit
to jeremy-hiatt/ostree
that referenced
this issue
Mar 8, 2018
…e_summary() Ensure that the metadata object is built up with the signatures from all keys passed to ostree_repo_add_gpg_signature_summary(). Previously only the signature from the last key would end up in the metadata. Closes: ostreedev#1488
jeremy-hiatt
added a commit
to jeremy-hiatt/ostree
that referenced
this issue
Mar 8, 2018
Ensure that the metadata object is built up with the signatures from all keys passed to ostree_repo_add_gpg_signature_summary(). Previously only the signature from the last key would end up in the metadata. Closes: ostreedev#1488
jeremy-hiatt
added a commit
to jeremy-hiatt/ostree
that referenced
this issue
Mar 8, 2018
Ensure that the metadata object is built up with the signatures from all keys passed to ostree_repo_add_gpg_signature_summary(). Previously only the signature from the last key would end up in the metadata. Closes: ostreedev#1488
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When the
--gpg-sign=<key>
flag is specified multiple times, only the last signature ends up in thesummary.sig
file. I'm working on a pull request that will fix the problem.The text was updated successfully, but these errors were encountered: