-
-
Notifications
You must be signed in to change notification settings - Fork 346
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
Fix GPG Key Import Error #3208
Fix GPG Key Import Error #3208
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
printf
interprets its first argument specially, as a format string, so it will do weird things if our file ever contains a percent sign character. Is there a reason you chose that command?
I was following some posts relating to importing this and it worked. Being a base64 encoded string, a percent sign shall not be an issue.
|
Try those commands wtih |
Or another option is no command at all, with here-strings:
|
Happy for you to go with whatever seems the neatest, if it doesn't work we can always change it. The no command at all seems pretty good to me. |
Works! Just a few loose ends to tie up.
|
GPG wasn't working with how the private key was being retrieved from however the key was being exposed resulting in nothing being imported.
The base64 encoded export (
gpg --export-secret-keys debian@ksp-ckan.space|base64
) seems to work just fine.I've adjusted the expiry as it probably isn't necessary for this use case.