Re: [Rpm-maint] [rpm-software-management/rpm] Verify that all OpenPGP signatures are a single signature packet (Issue #2233)

2022-10-18 Thread Demi Marie Obenour
Closed #2233 as completed. -- Reply to this email directly or view it on GitHub: https://github.com/rpm-software-management/rpm/issues/2233#event-7614349188 You are receiving this because you are subscribed to this thread. Message ID: ___ Rpm-maint

Re: [Rpm-maint] [rpm-software-management/rpm] Verify that all OpenPGP signatures are a single signature packet (Issue #2233)

2022-10-18 Thread Demi Marie Obenour
@nwalfield: then there is no bug, closing. -- Reply to this email directly or view it on GitHub: https://github.com/rpm-software-management/rpm/issues/2233#issuecomment-1282830219 You are receiving this because you are subscribed to this thread. Message ID:

Re: [Rpm-maint] [rpm-software-management/rpm] Verify that all OpenPGP signatures are a single signature packet (Issue #2233)

2022-10-18 Thread Neal H. Walfield
In `pgpPrtParams`, [`rpm-sequoia` checks that there is exactly one signature packet](https://github.com/rpm-software-management/rpm-sequoia/blob/main/src/lib.rs#L951). Can you please provide a reproducer for this bug. -- Reply to this email directly or view it on GitHub:

Re: [Rpm-maint] [rpm-software-management/rpm] Verify that all OpenPGP signatures are a single signature packet (Issue #2233)

2022-10-18 Thread Neal H. Walfield
Can you explain what you are trying to accomplish. Is your claim that an rpm signature should be exactly one signature package and a literal data packet? Out of curiosity, how are multiple signatures handled in rpm? -- Reply to this email directly or view it on GitHub:

[Rpm-maint] [rpm-software-management/rpm] Verify that all OpenPGP signatures are a single signature packet (Issue #2233)

2022-10-18 Thread Demi Marie Obenour
This is enforced by the current in-tree parser, but (presumably) not by the Sequoia parser. It does not require parsing the contents at all, merely the framing. I am willing to make a patch. -- Reply to this email directly or view it on GitHub: