Well, it seems it would be helpful to have some advice here. In my local setup,
packets analysis code detects the following,
in that order:
`
PGPTAG_PUBLIC_KEY; [1] public key id saved
PGPTAG_SIGNATURE
PGPSUBTYPE_SIG_CREATE_TIME
PGPSUBTYPE_REVOKE_REASON
This adds checks that padding is zeroed and that regions are internally
consistent. It also adds a check that the padding is of minimum length.
Fixes #1572.
You can view, comment on, or merge this pull request online at:
https://github.com/rpm-software-management/rpm/pull/1613
-- Commit
@DemiMarie pushed 1 commit.
40443f613f7945df470f1ee6561471d91cda15ce Check that padding is zeroed and
regions are consistent
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
> Well, it seems it would be helpful to have some advice here. In my local
> setup, packets analysis code detects the following,
> in that order:
>
> ```
>PGPTAG_PUBLIC_KEY; [1] public key id saved
>
>PGPTAG_SIGNATURE
>
> PGPSUBTYPE_SIG_CREATE_TIME
>
Thoughts?
--
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/1614___
Rpm-maint mailing list
Rpm-maint@lists.rpm.org