RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
When an IP range is set within the ssh_config the remote host is not checked against the IP range.

Version-Release number of selected component (if applicable):openssh-clients-5.3p1-104.el6_6.1.x86_64


How reproducible:100%


Steps to Reproduce:
1. create a host.example.com with an address on 192.168.1.10
2. add the following text to your /etc/ssh/ssh_config file, above the Host * settings

Host 192.168.1.*
 PasswordAuthentication no
 RSAAuthentication no

3. ssh 192.168.1.10, no password or RSA auth used
4. ssh host.example.com, password and RSA auth accepted

Actual results:
The same IP address has different ssh client settings

Expected results:
Since ssh is connecting to an IP address with specified config options, it should consult them.

Additional info:
The expected behavior may be a bit unclear for if there are custom settings for both the name and the address.....

    Thank you for taking the time to enter a bug report with us. We appreciate the feedback and look to use reports such as this to guide our efforts at improving our products. That being said, this bug tracking system is not a mechanism for requesting support, and we are not able to  guarantee the timeliness or suitability of a resolution.

    If this issue is critical or in any way time sensitive, please raise a ticket through your regular Red Hat support channels to make certain  it receives the proper attention and prioritization to assure a timely resolution. 

    For information on how to contact the Red Hat production support team, please visit:

    http://www.redhat.com/en/services/support#howto



From my point of view, it is clearly stated in man ssh_config, that:
> [...] The host is the hostname argument given on the command line (i.e. the name is not converted to a canonicalized host name before matching).
If you feel it is wrong, feel free to consult it with Support.