Rpm supports uncompressed payload as it is (see commit
81acadbf1f55d128d733b5d9552276b4679ac682 and
9666e8c297515910674e7a4122016e038251664b), but that doesn't help the deltarpm
case as this is a build-time thing.
I did consider adding a separate digest for the uncompressed data back when
adding RPMTAG_PAYLOADDIGEST (there are various uses for the data), but to
sanely do so would require teaching rpmio to calculate digests both pre- and/or
post-(de)compression per request.
Somehow permitting the payload bits to differ from what was created at
build-time would be a pretty significant change for rpm, but I agree there's a
point in it: ultimately it's the authenticity of delivered bits that matter,
not the delivery box (of compression). I'll need to think about this.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/861#issuecomment-534903573
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
