Dne 21. 02. 23 v 20:52 Michael McLean napsal(a):
Koji instances have control over how they run prune-signed-copies. It
is possible to not run it at all
The only difference between a signed copy and the original is the
signature header, which is kept under the sigcache dir even when a
signed copy is deleted. Signed copies can be recreated with a call to
writeSignedRPM, which simply splices the requested header in to make
I wonder why the signed copies don't replace the originals, if there is
no difference? Why the unsigned copies are kept while the signed are
not. Why the signed copies are not directly accessible from the Koji UI?
When I was first informed about the IMA signing plan, I was told that
the ima signatures were all in the signature header. If this is not
the case, then the whole process is deeply flawed.
On Tue, Feb 21, 2023 at 2:31 PM Frank Ch. Eigler <fche(a)redhat.com> wrote:
Recently, fedora koji has started applying per-file (IMA) signatures
to RPMs it has built. This is in addition to the overall GPG
signature of the RPM payload as a whole. While this extra capability
is not yet fully developed in userspace, we do have one ready user
(elfutils debuginfod ), which is unfortunately frustrated by a
policy in the koji code base.
That policy problem is the periodic pruning of signed RPMs. That is,
"koji prune-signed-copies" is run on the fedora infra every now and
then. This operation nukes data/signed/KEYHEX/ARCH/N-V-R.rpm files.
While it leaves behind data/sigcache/ARCH/*, those files appear not to
include the IMA signature content. That means the IMA signatures are
simply lost, like tears in rain.
We'd like to correct this somehow - to make the IMA signatures
available indefinitely - at least as long as the built RPMs stay of
any interest. (That means: not restricted to the most-recent-update
of a given fedora release.)
1) have the pruning operate by replacing the unsigned binaries
signed ones (hardlink or rename)?
2) have the pruning operate on the unsigned binaries, preserving the
3) preserve the IMA signature content somewhere nearby (sigcache?)
to give us a chance at finding the data there after a prune
4) ---> some other way? <---
koji-devel mailing list -- koji-devel(a)lists.fedorahosted.org
To unsubscribe send an email to
Fedora Code of Conduct:
Do not reply to spam, report it:
koji-devel mailing list --koji-devel(a)lists.fedorahosted.org
To unsubscribe send an email tokoji-devel-leave(a)lists.fedorahosted.org
Fedora Code of Conduct:https://docs.fedoraproject.org/en-US/project/code-of-conduct/
Do not reply to spam, report it:https://pagure.io/fedora-infrastructure/new_issue