[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openssh-bugs
Subject:    [Bug 2831] New: ProxyJump self-exec construction ignores path-to-self, exec's wrong ssh
From:       bugzilla-daemon () bugzilla ! mindrot ! org
Date:       2018-02-12 22:20:48
Message-ID: bug-2831-705 () https ! bugzilla ! mindrot ! org/
[Download RAW message or body]

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

            Bug ID: 2831
           Summary: ProxyJump self-exec construction ignores path-to-self,
                    exec's wrong ssh
           Product: Portable OpenSSH
           Version: 7.6p1
          Hardware: 68k
                OS: Mac OS X
            Status: NEW
          Severity: enhancement
          Priority: P5
         Component: ssh
          Assignee: unassigned-bugs@mindrot.org
          Reporter: phil.pennock@globnix.org

On a system with an older release in /usr/bin and current OpenSSH in
/usr/local/bin, but for $reasons keeping /usr/bin first in the $PATH,
having "ssh" exec itself using "ssh" as argv[0] will execute the wrong
SSH.  That's what ProxyJump does.

Encountered via: git using core.sshCommand as a setting, and a config
file using ProxyJump.  The child ssh will complain about the invalid
configuration directive.


Since config can be read by "sftp" etc, I suspect that one fix is to
look for a path separator in "our" argv[0] and if found, then replace
the last component with "ssh" and use the result as the new process'
argv[0], otherwise fall back to "ssh".

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
openssh-bugs mailing list
openssh-bugs@mindrot.org
https://lists.mindrot.org/mailman/listinfo/openssh-bugs
[prev in list] [next in list] [prev in thread] [next in thread]