[Bug 2385] ssh does not document relative priorities among various methods of specifying login name
bugzilla-daemon at mindrot.org
bugzilla-daemon at mindrot.org
Tue Apr 28 15:04:10 AEST 2015
https://bugzilla.mindrot.org/show_bug.cgi?id=2385
Darren Tucker <dtucker at zip.com.au> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dtucker at zip.com.au
Status|NEW |ASSIGNED
--- Comment #1 from Darren Tucker <dtucker at zip.com.au> ---
(In reply to Jakub Jelen from comment #0)
> Created attachment 2596 [details]
> proposed patch
>
> +++ This bug was created as a clone from Red Hat bugzilla 1196989 +++
>
> Description of problem:
> I am aware of following methods of specifying the login name to the
> ssh program:
>
> 1. /etc/ssh/ssh_config
> 2. ~/.ssh/config
> 3. -l option to ssh
> 4. user at hostname syntax
>
> The SSH(1) man page does not clarify behaviour in case multiple of
> the above options are use simultaneously.
It's in ssh_config(5). ssh(1) says:
"""
ssh may additionally obtain configuration data from a per-user
configuration file and a system-wide configuration file. The file
format and configuration options are described in ssh_config(5).
"""
which in turn says:
"""
ssh(1) obtains configuration data from the following sources in the
following order:
1. command-line options
2. user's configuration file (~/.ssh/config)
3. system-wide configuration file (/usr/local/etc/ssh_config)
For each parameter, the first obtained value will be used.
"""
I don't think the -l user / user@ behaviour is documented, though.
> Even the ssh -vv output does not log any message in such cases.
If you're referring specifically to the username that ends up being
used, this was recently added:
http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/usr.bin/ssh/sshconnect.c.diff?r1=1.260&r2=1.261
--
You are receiving this mail because:
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.
More information about the openssh-bugs
mailing list