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
{{ message }}
This repository has been archived by the owner on Oct 1, 2024. It is now read-only.
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"?
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.
The text was updated successfully, but these errors were encountered: