Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEATURE REQUEST] Add parameters to limit gpg.verify to a set of explicit keys #63166

Closed
lkubb opened this issue Dec 1, 2022 · 0 comments · Fixed by #63168
Closed

[FEATURE REQUEST] Add parameters to limit gpg.verify to a set of explicit keys #63166

lkubb opened this issue Dec 1, 2022 · 0 comments · Fixed by #63168
Labels
Execution-Module Feature new functionality including changes to functionality and code refactors, etc. needs-triage

Comments

@lkubb
Copy link
Contributor

lkubb commented Dec 1, 2022

Is your feature request related to a problem? Please describe.
If my doctor advises me on the latest band I should listen to and my friends write me prescriptions, I might have a problem. I trust them both, but this trust depends on the scope. apt realized this when it deprecated apt-key.

I would like to be able to verify that a signature on a file is from the signer(s) I expect it to be from, not some rando whose key I imported years ago.

Describe the solution you'd like
Add signed_by_any/signed_by_all parameters to gpg.verify, which make sure that only signatures by keys with specified fingerprints result in final success.

Describe alternatives you've considered
Using a separate keyring for each set of keys. This implies a separate gnupghome in Salt currently, since #59783 has not been implemented yet (coming).

@lkubb lkubb added Feature new functionality including changes to functionality and code refactors, etc. needs-triage labels Dec 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Execution-Module Feature new functionality including changes to functionality and code refactors, etc. needs-triage
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants