Okay, I confirmed that it's wrong to assume that: ExecStartPost=/usr/bin/systemctl --user set-environment SSH_AUTH_SOCK=/run/user/1000/openssh_agent
will do the right thing in the general case. This does correctly set the environment in the user manager, and if you launch an application like e.g.: $ systemd-run --user --wait --pipe -q -- ssh-add then the environment is inherited, and $SSH_AUTH_SOCK is set. But, if one has a session spawned by login(1), this is not going to happen. Maybe as a quick fix, we could patch openssh to try $XDR_RUNTIME_DIR/openssh_agent (the default) if $SSH_AUTH_SOCK is unset. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2125549 Title: ssh agent no longer work a questing upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2125549/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
