Skip to content
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

Automatic signature not working with gpg 2.2.19 #133

Open
c8y3 opened this issue Jul 1, 2022 · 1 comment
Open

Automatic signature not working with gpg 2.2.19 #133

c8y3 opened this issue Jul 1, 2022 · 1 comment

Comments

@c8y3
Copy link

c8y3 commented Jul 1, 2022

Automatic signature (without user input) of the rpm fails with gpg 2.2.19.
If my understanding is correct, it seems that the script (coded in the RPMSigner) that uses "expect" to automatically input the passphrase is not working as expected. Maybe because recent versions of gpg use gpp-agent and the pinentry program is different from before.

Instead of using expect, would it be possible to evolve the RPMSigner so that it calls rpm --addsign with the following additional argument: --define "_gpg_sign_cmd_extra_args --pinentry-mode loopback --passphrase $PIN"?

This issue seems related to the following discussion: https://unix.stackexchange.com/questions/328601/rpmsign-with-cli-password-prompt.

Thank you.

@c8y3
Copy link
Author

c8y3 commented Jul 1, 2022

If my understanding of this piece of code is correct (https://github.com/apache/maven-gpg-plugin/blob/master/src/main/java/org/apache/maven/plugins/gpg/GpgSigner.java) the change of gpg behavior started with gpg 2.1.
So, probably the RPMSigner should still need to use the expect script with older versions of gpg.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant