[Bug 2621] ControlMaster started by scp (non-ssh?) doesn't forward agent

bugzilla-daemon at bugzilla.mindrot.org bugzilla-daemon at bugzilla.mindrot.org
Sat Sep 16 00:03:49 AEST 2017


https://bugzilla.mindrot.org/show_bug.cgi?id=2621

Matthijs Kooijman <matthijs at stdin.nl> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |matthijs at stdin.nl

--- Comment #1 from Matthijs Kooijman <matthijs at stdin.nl> ---
This seems a more general problem: Agent forwarding seems only to
happen when starting a new ControlMaster. If ssh re-uses an existing
ControlMaster, the -A option seems to be (silently!) ignored:

Passing -A to the master works:

matthijs at grubby:~$ ssh tika-login -o ControlMaster=yes -o
ControlPath=/tmp/foo -A
matthijs at login:~$ echo $SSH_AUTH_SOCK
/tmp/ssh-Kmwf42CH18/agent.3830
matthijs at login:~$ logout
Connection to tikatika.nl closed.

But passing -A to a "slave" ssh does not:

matthijs at grubby:~$ ssh tika-login -o ControlMaster=yes -o
ControlPath=/tmp/foo

And in another terminal:

matthijs at grubby:~$ ssh -o ControlPath=/tmp/foo tika-login -A
matthijs at login:~$ echo $SSH_AUTH_SOCK

matthijs at login:~$ 

I can imagine there's a technical reason to not support this, but then
at least it should be documented and passing -A should show an error or
warning (possibly depending on ExitOnForwardFailure).

-- 
You are receiving this mail because:
You are watching the assignee of the bug.


More information about the openssh-bugs mailing list