Bugzilla – Bug 1065404
gnupg not usable for signing within mutt session from remote
Last modified: 2019-07-18 16:46:41 UTC
Currently it is not possible (anymore) to spawn a second gpg-agent with gnupg 2.2.1 as then the gpg-agent exist with an error that there is already a running gpg-agent. This rise the problem that the already running gpg-agent starts the pinentry below the already running X session which does not work for mutt used via slogin from remote. This hardcoded socket below /run/user/<uid> breaks the possiblity to be able to use gpg via slogin! and pinetry is not able to detect which application and it environmet is calling via gpg-agent for a passphrase! I'm using ignore-invalid-option allow-emacs-pinentry ignore-invalid-option allow-loopback-pinentry in ~/.gnupg/gpg-agent.conf
This is essentially the same problem as bug 1061963, isn't it?
(In reply to Andreas Stieger from comment #1) > This is essentially the same problem as bug 1061963, isn't it? I have mentioned this in bug #1061963 yes but bug #1061963 is original about the keyserver refresh failed: IPC syntax error error what breaks sending/reveiving/updating keys. I'm currently can not work below Tumbleweed for home office .. the only solution I see is a switch from pinentry-program /usr/bin/pinentry to pinentry-program /usr/bin/pinentry-curses (or the tty version) in ~/.gnupg/gpg-agetn.conf followed by gpgconf --reload gpg-agemt or gpg-connect-agent reloadagent /bye The mutt has an enabled gpgme API and I'd like to use this without any workarounds
Since version 2.1 the standard use of gpg-agent is to be started on demand and not by the X11 start up scripts. See comments: https://bugzilla.suse.com/show_bug.cgi?id=1124847#c9 https://bugzilla.suse.com/show_bug.cgi?id=1124847#c10 We could try to fix this only in Factory.