pulp
As a user, Pulp is able to verify package signatures, and reject unsigned or invalidly-signed packages
Author: mped (mped)
Redmine Issue: 7820, https://pulp.plan.io/issues/7820
In Pulp2 when carrying out a synchronisation it is possible to add the flag --require-signature, to ensure that synched packages are signed, please can this feature be added to Pulp3.
Additionally please can support for allowed-keys also be included.
Thanks
Matt
From: @ggainey (ggainey) Date: 2020-11-12T16:30:59Z
This would be an attribute at the repository-level, and would apply to copy and upload operations as well as sync.
A thought - What happens if you turn it on when there is already unsigned content in the repo? (allow? fail with error?)
@mped - how critical is this for you? Does it, for example, block moving to Pulp3?
From: mped (mped) Date: 2020-11-16T18:42:15Z
Hi ggainey,
This will block us moving to Pulp3 however we are still quite a few months away from that migration, until some other features of Pulp3 mature and are no longer in techpreview, so it isn't critical for us at the moment. It is more we have come across a need to turn it on one of our Pulp2 repos, so just need to know the feature will eventually make it Pulp 3.
One thought around turning it on with a repo with already unsigned content is are you able to warn that this is the case, and then the end user can chose if they want to have those content units removed, or even allow the user to specify they should be removed if unisgned units exist?
Thanks
Matt
From: @dralley (dalley) Date: 2021-06-09T03:52:42Z
We should take a look at verifying metadata signatures as well.
We have a similar feature request: we'd also like to verify that the signature's key is in a list of accepted keys.
Not sure if I should file a separate issue for this or not?
And also we'd be interested in the package upload or add to repository use case (as opposed to syncing).
