Binary GnuPG keys downloaded by 'ansible.builtin.apt_key' were corrupted #74474
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.
SUMMARY
When importing a key by the
apt_key
module, it gets corrupted and not imported in the case of a binary key (not a textual “armored” key). Ansible tries to convert string data, but some data is lost on conversion, which results in a GnuPG error. This is a bug because binary data should not be converted using theto_native
function.ISSUE TYPE
COMPONENT NAME
ansible.builtin.apt_key module
ADDITIONAL INFORMATION
Fixes #74424
Augmented by #74483
To reproduce this error, create the following files:
Fie
Vagrantfile
file:The
test.yaml
file:and run
vagrant up
Expected Results:
Key imported without a problem
Actual Results:
Relevant file:
lib/ansible/modules/apt_key.py