Okay no further comments / feedback, back to the drawing board for now.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Closed #1050.
--
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/pull/1050#event-3669947490___
Rpm-maint mailing list
Oh and to be clear, this is little more than a draft at this point and ideas +
suggestions are very welcome.
I originally did this in spring of 2017 but got side-tracked with 4.14 release
and RHEL 8 and whatnot, and the work very nearly got lost forever (it would
have, if it wasn't for
It could be multiple groups or whatever, but certainly not about new
algorithms. It's kinda intentionally loosely defined to the point of being
undefined to allow creative use.
The "name" part was called "role" in earlier versions, which might give
different ideas about its usage, but decided
What's the purpose of the 'name' part? Is this about supporting signatures from
multiple groups? Or is this about supporting new pubkey algorithms (e.g.
ed22519)?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
This pull request **introduces 1 alert** when merging
cb14ea4623079300c9fffb748a0f63518e64c1b5 into
d937b04fb1cb5d3ca303bd458169c352a4b52669 - [view on
LGTM.com](https://lgtm.com/projects/g/rpm-software-management/rpm/rev/pr-23e1bbee5a8ca504ba89111edb6f53d91798e1d8)
**new alerts:**
* 1 for
Add support for multiple, named signatures per package.
Named signatures are stored as a name:base64 encoded string array in
RPMTAG_OPENPGPHEADER, name is an arbitrary \0-terminated string
and is part of the signed data (appended after actual package data).
These are always header-only
