You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some provider we use like Google, Hashicorp only provide ASCII armored gpg key (if I did not miss anything), which seems to not work with the apt keyring mechanism implemented to fix #1034 as from my understanding apt expect binary gpg keys.
Describe the Solution You Would Like
Having a boolean parameter in apt::keyring to specify if the key is armored and dearmor it if necessary
Describe Alternatives You've Considered
Manually dearmore GPG keys and self host them either in puppet code or third party solution
Additional Context
n/a
The text was updated successfully, but these errors were encountered:
ASCII armored keys are supported. You have to name them with a .asc extension if ASCII armored, and .gpg if binary. This is an APT thing, not an issue with this module. This is documented:
You can fetch GPG keys via HTTP, Puppet URI, or local filesystem. The key can be in GPG binary format, or ASCII armored, but the filename should have the appropriate extension (`.gpg` for keys in binary format; or `.asc` for ASCII armored keys).
Also note that there is a bug in APT that causes it to fail if ASCII armored keys use Windows/DOS text format. You'll want to dos2unix the file first, if you find such a key. Reference: https://salsa.debian.org/apt-team/apt/-/merge_requests/309
Use Case
Some provider we use like Google, Hashicorp only provide ASCII armored gpg key (if I did not miss anything), which seems to not work with the apt keyring mechanism implemented to fix #1034 as from my understanding apt expect binary gpg keys.
Describe the Solution You Would Like
Having a boolean parameter in apt::keyring to specify if the key is armored and dearmor it if necessary
Describe Alternatives You've Considered
Manually dearmore GPG keys and self host them either in puppet code or third party solution
Additional Context
n/a
The text was updated successfully, but these errors were encountered: