Skip to content

Return UntrustedKey also for unsupported/disabled keys#109

Merged
github-actions[bot] merged 1 commit intorpm-software-management:mainfrom
Jakuje:untrusted-key
Apr 24, 2026
Merged

Return UntrustedKey also for unsupported/disabled keys#109
github-actions[bot] merged 1 commit intorpm-software-management:mainfrom
Jakuje:untrusted-key

Conversation

@Jakuje
Copy link
Copy Markdown
Collaborator

@Jakuje Jakuje commented Feb 24, 2026

Follow-up from #107, where we merged the unknown signatures, but not unknown keys during import. This was left for further discussion if this is the right thing to do.

The RPM needs to distinguish between completely broken keys and keys
that are "just" untrusted by the policy.

Similarly with signatures on RPMs we can return the NonTrusted return
value, that can be used by RPM to differentiate these errors and allow
filtering valid certificates when a file contains more of them.

Signed-off-by: Jakub Jelen <jjelen@redhat.com>
Co-authored-by: Neal H. Walfield <neal@sequoia-pgp.org>
@nwalfield
Copy link
Copy Markdown
Collaborator

I modified the MR as discussed: if using the standard policy fails, try with the null policy. If using the null policy says Ok, then return NotTrusted. If using the null policy says Err, then the signatures are probably bad.

@nwalfield nwalfield marked this pull request as ready for review April 24, 2026 16:58
@nwalfield
Copy link
Copy Markdown
Collaborator

/fast-forward

@github-actions github-actions Bot merged commit 5a576b2 into rpm-software-management:main Apr 24, 2026
5 of 6 checks passed
@Jakuje
Copy link
Copy Markdown
Collaborator Author

Jakuje commented Apr 24, 2026

Thank you! I will give it a try with the rpm tests!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants