(In reply to Robert Riemann from comment #23) > I use gnupg instead and it works for me even better than ssh agent. > Gnupg can be autostarted via systemd.
Using gpg-agent has the disadvantage that it makes a secret copy of the private SSH keys in `~/.gnupg/private-keys-v1.d/` that cannot be listed or edited from the `gpg` command-line tool. However, it's also possible to automatically start ssh-agent (and optionally tell it to use ksshaskpass) for Plasma Wayland sessions via a systemd user service. The following unit configuration file could be placed in `$HOME/.config/systemd/user/ssh-agent.service`, after which the service can be enabled and started with `systemctl --user enable --now ssh-agent`. ``` [Unit] Description=OpenSSH authentication agent Documentation=man:ssh-agent(1) man:ssh-add(1) man:ssh(1) ConditionEnvironment=!SSH_AGENT_PID PartOf=plasma-workspace-wayland.target Before=plasma-workspace-wayland.target [Service] Type=simple Environment=SSH_AUTH_SOCK=%t/ssh-agent.socket # Remove the following line if you don't want to use ksshaskpass Environment=SSH_ASKPASS=/usr/libexec/ssh/ksshaskpass ExecStart=/usr/bin/ssh-agent -D -a $SSH_AUTH_SOCK ExecStartPost=/usr/bin/systemctl --user import-environment SSH_AUTH_SOCK [Install] WantedBy=plasma-workspace-wayland.target ``` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2024937 Title: ssh-agent is not started via startplasma-wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/2024937/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
