-
Notifications
You must be signed in to change notification settings - Fork 33
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
custom signing key for images does not work gnupg 2.4 / flatcar beta #1471
Comments
I can't comment on overriding the trusted key, but dirmngr is missing because gnupg has been built with |
thanks, removing the masking of ssl in |
I may make that change, but it's not the proper fix here. I understand the issue now and am discussing the solution. We probably want |
Using a custom key was recently broken by a GnuPG update. The Flatcar key is not imported when a custom key is given, but we still reference the Flatcar key with --trusted-key regardless, causing gpg to attempt to download the key from a keyserver. This fails because we no longer ship the necessary dirmngr binary, which is now only built when GnuPG has GnuTLS support enabled. Enabling GnuTLS support works around the problem, but it is not the proper fix. --trusted-key causes gpg to trust the given key, even though there is no secret key present. This is unnecessary, as the key would be trusted anyway, albeit with a warning. --assert-signer makes more sense, as this ensures the file was signed specifically by the given key rather than some other key you happen to have in your keyring. --assert-signer only accepts the long key ID, not the key file. There is no way to discover the key ID of a key that has just been imported, but you can get it from the original key file in a stable manner. Closes: flatcar/Flatcar#1471 Signed-off-by: James Le Cuirot <[email protected]>
Description
since 3913.1.0 in the beta channel gnupg 2.4 is used, this seems to break usage of custom signing keys due to dirmngr not being present in the installer image and the installer using hardcoded key in the --trusted-key argument despite running
flatcar-install -k customkey
Impact
self signed images cannot be installed
Environment and steps to reproduce
gnupg 2.4 on flatcar 3941.1.0
verification failed here despite
gpg: Good signature from "testt" [unknown]
, it exited with code 2in comparison on flatcar 3874.1.0:
verification succeeded
Expected behavior
self signed images can be installed with verification
If we could override the --trusted-key in the flatcar installer gnugpg would not try to invoke dirmngr and it would work but the trusted key is hardcoded in the installer.
The text was updated successfully, but these errors were encountered: