On 3/13/20 10:11 AM, Stasiek Michalski wrote:
On Thu, Mar 12, 2020 at 23:06, Wolfgang Rosenauer <wolfgang@rosenauer.org> wrote:
Hi,
Am 12.03.20 um 22:14 schrieb Johannes Kastl:
On 12.03.20 at 21:06 Johannes Kastl wrote:
Johannes (off looking how to disable the gpg-agent start in KDE PLasma...)
Apparently this is being handled in /etc/X11/xdm/scripts/09-ssh-vars and /etc/X11/xdm/scripts/10-gpg-agent, at least that were the only places I found so far.
Setting usessh and usegpg to no. Enable the systemd user sockets. Only thing I had to do was export SSH_AUTH_SOCK pointing to ~/.ssh/ssh_auth_sock, that I created as a link to /run/user/1000/gnupg/S.gpg-agent.ssh.
Now ssh-agent and gpg-agent are fine, I am asked for a passphrase when trying to use my SSH key.
Next stop: Wayland.
I was also running into gpg/ssh-agent issues when I switched to wayland. The outcome so far was https://bugzilla.suse.com/show_bug.cgi?id=1164872
I do not understand why the quite well working X11 setup is not used (similarly) for a wayland session,
This is a twofold problem from the packaging point of view at least. Non XDM specific scripts were very often installed in XDM scripts directory, which means that every desktop has to have XDM installed for no particular reason. If instead we used profile.d and xinit as the source of those scripts, we could avoid installing XDM and have the ability to use some of those scripts under Wayland.
Many of them would probably make more sense running as a systemd user service. We'd probably need to check that our presets stuff works with user services. For things like this one that have socket activation we really should just be configuring that right out of the box.
Now just somebody has to do it ;)
Yep -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B