Summary: | kde-base/kdebase-startkde, kde-plasma/plasma-workspace - gpg-agent shutdown fails with app-crypt/gnupg-2.1.3-r3 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Alexander E. Patrakov <patrakov> |
Component: | Current packages | Assignee: | Gentoo KDE team <kde> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | alunduil |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://www.gnupg.org/faq/whats-new-in-2.1.html#autostart | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Alexander E. Patrakov
2015-04-24 06:45:44 UTC
(In reply to Alexander E. Patrakov from comment #0) > > Unfortunately, gpgconf cannot be used to launch gpg-agent with ssh support. > This isn't entirely true, if "enable-ssh-support" is set in gpg-agent.conf it will launch with ssh support, and as 2.1 always use standard sockets as a reference the SSH_AUTH_SOCK stays constant (SSH_AUTH_SOCK=${HOME}/.gnupg/S.gpg-agent.ssh by default, or any other --homedir used). 2.1 will auto-launch gpg-agent when needed for its internal operations, this is what is not directly supported for ssh (it needs to have a running agent), which a gpgconf --launch gpg-agent does. I can confirm that gpgconf --launch gpg-agent with appropriate setting of the SSH_AUTH_SOCK environment variable does work as intended from the plasma or kde startup file. My current setup: startup: if [ -x /usr/bin/gpgconf ]; then gpgconf --launch gpg-agent export SSH_AUTH_SOCK=/run/user/$UID/gnupg/S.gpg-agent.ssh fi shutdown is currently empty but could easily do gpgconf --kill gpg-agent. This does work as expected. (In reply to Alex Brandt from comment #2) > I can confirm that gpgconf --launch gpg-agent with appropriate setting of > the SSH_AUTH_SOCK environment variable does work as intended from the plasma > or kde startup file. > > My current setup: > > startup: > > if [ -x /usr/bin/gpgconf ]; then > gpgconf --launch gpg-agent > export SSH_AUTH_SOCK=/run/user/$UID/gnupg/S.gpg-agent.ssh > fi > Just beware that this socket location changed in 2.1.13, for 2.1 branch earlier than that uses the location mentioned in my earlier comment. For versions of gnupg 2.0 it depends on whether gpg-agent is launched with use standard socket or not, but there the appropriate auth socket is reported back with the gpg-agent --daemon) . the test for gpgconf isn't sufficient to distinguish between these versions as it is also provided with gnupg 2.0. I've pushed a fix for this to the overlay for testing (thanks Kristian), to hit the main tree with Plasma 5.7.0. Since Plasma 4 is EOL the change probably will not be backported there however. https://gitweb.gentoo.org/proj/kde.git/commit/?id=ca6c861f8f54ccb7521ec91da98f73bab1f91e8a 5.7 is in the tree now with the fix. |