Your message dated Sun, 2 Apr 2017 02:24:42 +0100 with message-id <[email protected]> and subject line Re: Bug#788745: systemd user unit to start ssh-agent has caused the Debian Bug report #788745, regarding systemd user unit to start ssh-agent to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 788745: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788745 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: openssh-client Version: 1:6.7p1-6 Severity: wishlist Tags: patch Hi, I'm using the attached systemd user unit to startup ssh-agent. Cheers, Moritzdiff -Naur openssh-6.7p1.orig/debian/openssh-client.install openssh-6.7p1/debian/openssh-client.install --- openssh-6.7p1.orig/debian/openssh-client.install 2015-03-23 00:08:49.000000000 +0100 +++ openssh-6.7p1/debian/openssh-client.install 2015-06-11 11:33:20.443877625 +0200 @@ -35,3 +35,4 @@ # Upstart user job (only used under user sessions). debian/ssh-agent.user-session.upstart => usr/share/upstart/sessions/ssh-agent.conf +debian/ssh-agent.service => /usr/lib/systemd/user diff -Naur openssh-6.7p1.orig/debian/README.Debian openssh-6.7p1/debian/README.Debian --- openssh-6.7p1.orig/debian/README.Debian 2015-03-23 00:08:49.000000000 +0100 +++ openssh-6.7p1/debian/README.Debian 2015-06-11 11:31:27.618079976 +0200 @@ -229,6 +229,19 @@ copying /lib/systemd/system/ssh.socket to /etc/systemd/system/ssh.socket and modifying the ListenStream option. See systemd.socket(5) for details. +Starting ssh-agent with systemd +------------------------------- + +ssh-agent can be launched through a systemd user unit. The unit is shipped +as /usr/lib/systemd/user/ssh-agent.service. + +It needs to be enabled on a per-user basis by running + +systemctl --user enabled ssh-agent + +It creates a socket ssh-agent.socket inside the $XDG_RUNTIME_DIR directory, +so make sure your environment variable $SSH_AUTH_SOCK points to that. + -- Matthew Vernon <[email protected]> Colin Watson <[email protected]> diff -Naur openssh-6.7p1.orig/debian/ssh-agent.service openssh-6.7p1/debian/ssh-agent.service --- openssh-6.7p1.orig/debian/ssh-agent.service 1970-01-01 01:00:00.000000000 +0100 +++ openssh-6.7p1/debian/ssh-agent.service 2015-06-11 11:31:47.670372124 +0200 @@ -0,0 +1,11 @@ +[Unit] +Description=SSH authentication agent +Before=default.target + +[Service] +Type=forking +Environment=SSH_AUTH_SOCK=%t/ssh-agent.socket +ExecStart=/usr/bin/ssh-agent -a $SSH_AUTH_SOCK + +[Install] +WantedBy=default.target
--- End Message ---
--- Begin Message ---Source: openssh Source-Version: 1:7.2p2-8 On Sun, Jun 14, 2015 at 07:56:58PM +0200, Moritz Muehlenhoff wrote: > I'm using the attached systemd user unit to startup > ssh-agent. Thanks. I added a similar-in-spirit unit in response to #832445, having forgotten about this bug. Hopefully that meets your needs; if not, please let me know what needs to change and why. -- Colin Watson [[email protected]]
--- End Message ---
