[Bug 2385] New: ssh does not document relative priorities among various methods of specifying login name
bugzilla-daemon at mindrot.org
bugzilla-daemon at mindrot.org
Fri Apr 17 23:43:14 AEST 2015
https://bugzilla.mindrot.org/show_bug.cgi?id=2385
Bug ID: 2385
Summary: ssh does not document relative priorities among
various methods of specifying login name
Product: Portable OpenSSH
Version: 6.8p1
Hardware: Other
OS: Linux
Status: NEW
Severity: enhancement
Priority: P5
Component: Documentation
Assignee: unassigned-bugs at mindrot.org
Reporter: jjelen at redhat.com
Created attachment 2596
--> https://bugzilla.mindrot.org/attachment.cgi?id=2596&action=edit
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. Even the ssh -vv output does not
log any message in such cases.
[...]
--- Additional comments ---
>From my POV, it would be useful to mention these priorities in
documentation. Also I would mention that if nothing defined, username
is obtained from current user. And where does live priority of -o
switch.
Based on my experience and observation, the exhaustive explanation of
priorities would look like this:
1. user specified before @ character in hostname string
2. login_name specified using -l switch
3. User option provided as a parametr 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.
(as attached documentation source in path, this is for readability)
Feel free to comment if I missed something or you would spell it
better. It is not critical, but nice to have thing.
--
You are receiving this mail because:
You are watching the assignee of the bug.
More information about the openssh-bugs
mailing list