fix: Explicitly set private key type for GPG key generation #11944
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
While running
make test-local
on a Fedora 37 box, the GnuPG key creation failed in the unit tests. After doing some research, it seems that recent versions of GnuPG have a bug [1] when specifying the key type to be generated asDefault
, so this PR explicitly sets it to RSA. We really don't care about the long term security of the private key, as it's only used to initialize the trust db and is transient by nature.Submitting this fix before it hits us :)
Current version of GnuPG in our most recent release (v2.5.4):
Version from Fedora 37:
[1] https://dev.gnupg.org/T5444
Signed-off-by: jannfis jann@mistrust.net
Note on DCO:
If the DCO action in the integration test fails, one or more of your commits are not signed off. Please click on the Details link next to the DCO action for instructions on how to resolve this.
Checklist: