[Bug 2849] New: OpenSSH 7.7p1 uses login_name value instead of user at hostname

[bugzilla-daemon at bugzilla.mindrot.org]

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

            Bug ID: 2849
           Summary: OpenSSH 7.7p1 uses login_name value instead of
                    user at hostname
           Product: Portable OpenSSH
           Version: 7.6p1
          Hardware: amd64
                OS: Windows 10
            Status: NEW
          Severity: normal
          Priority: P5
         Component: ssh
          Assignee: unassigned-bugs at mindrot.org
          Reporter: mark.earl.waite at gmail.com

OpenSSH bug 2385 notes that the observed order of evaluation of the
login_name is:

>      1.   user specified before @ character in hostname string
>      2.   login_name specified using -l switch
>      3.   User option provided as a parameter to -o switch
>      4.   User option in matching Host block from per-user config ~/.ssh/config
>      5.   User option in matching Host block from systemwide config /etc/ssh/ssh_config
> If there is nothing from above specified, username on local terminal is used.

That matches the behavior of OpenSSH 7.6 and earlier.

OpenSSH 7.7p1 has changed the order of evaluation of the login_name. 
It is now evaluated as:

     1.   login_name specified using -l switch
     2.   user specified before @ character in hostname string
     3.   User option provided as a parameter to -o switch
     4.   User option in matching Host block from per-user config
~/.ssh/config
     5.   User option in matching Host block from systemwide config
/etc/ssh/ssh_config
If there is nothing from above specified, username on local terminal is
used.

The order of evaluation change exposed an inconsistency in the Jenkins
git plugin which was inadvertently relying on the earlier order of
evaluation.  

See JENKINS-50573 for the details of the Jenkins bug.

See Git for Windows issue 1616 for the details investigated by Johannes
Schindelein of the Git for Windows project.  Johannes also references a
possible fix in the Git for Windows issue.

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