Hmm. Just realized that we're accidentally using ASCII-armored signatures when
signing with Sequoia, whereas GPG always used binary signatures. And when we
then base64 encode that, it gets silly. But that also made me realize that we
could use ASCII armored signatures as-is in the RPMTAG_OPENPGP, somehow this
option never even crossed my mind, I was so fixated on the gpg-era default. We
could still change this of course - thoughts?
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/3385#issuecomment-2505597692
You are receiving this because you are subscribed to this thread.
Message ID: <rpm-software-management/rpm/issues/3385/[email protected]>
_______________________________________________
Rpm-maint mailing list
[email protected]
https://lists.rpm.org/mailman/listinfo/rpm-maint
