My bad for not noticing.
Good that padding has been added by adding (apparently) 0x1000 to the data size:
`0060: 8ead e801 0006 1074 ...t`
Adding a "free space" tag (as @rpm5.org) provides an indication that the
signature header is padded.
Meanwhile, the
Ah, you have added RPMSIGTAG_RESERVEDSPACE already which I was not expecting.
The (minor but annoying problems) with the assignment to 1008 is that
RPMSIGTAG_RESERVEDSPACE collides with RPMTAG_INSTALLTIME, and will not sort
correctly to the end of an immutable region data section as a "free
The recently added RPMTAG_PAYLOADDIGEST computes a digest on the compressed
payload.
Perhaps now is the time to change the plaintext used to be the uncompressed
rather than the compressed archive payload?
The benefit of the digest on the uncompressed archive is that the digest
becomes immune
