Red Hat Bugzilla – Bug 159268
RFE: Log IPv4 adresses as IPv4, not IPv6.
Last modified: 2007-11-30 17:07:18 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050512 Red Hat/1.7.8-126.96.36.199
Description of problem:
sshd logs all connection attempts as IPv6 addresses, even if they were really
May 29 18:58:06 homer sshd: Failed password for root from ::ffff:188.8.131.52 port 49674 ssh2
May 29 18:58:07 homer sshd: Invalid user admin from ::ffff:184.108.40.206
This clutters up the logs (and hence logwatch mails) and is generally unsightly.
A workaround is to add
to /etc/ssh/sshd_conf, but that disables listening to ipv6 alltogether,
which isn't really what I want.
Upstream has a patch to fix this. From the 4.1p1 changelog:
- (dtucker) [canohost.c] normalise socket addresses returned by
get_remote_hostname(). This means that IPv4 addresses in log messages
on IPv6 enabled machines will no longer be prefixed by "::ffff:" and
AllowUsers, DenyUsers, AllowGroups, DenyGroups will match IPv4-style
addresses only for 4-in-6 mapped connections, regardless of whether
or not the machine is IPv6 enabled. ok djm@
Please backport this.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. install openssh
2. ssh to it (via ipv4)
3. check out the logs.
Actual Results: encapsulated ipv4 addresses.
Expected Results: proper dotted-quad ipv4 addressses.
In order to file a RHEL feature request, please either contact Red Hat's
Technical Support line at 888-REDHAT-1 or file a web ticket at
http://www.redhat.com/apps/support/. Bugzilla is not an official support
channel, has no response guarantees, and may not route your request to the
correct area to assist you. Using the official support channels above will
guarantee that your issue is handled appropriately and routed to the
individual or group which can best assist you with this issue and will also
allow Red Hat to track the issue, ensuring that any applicable feature
addition is included in all releases and is not dropped from a future update
or major release.
*** Bug 172181 has been marked as a duplicate of this bug. ***
We have the academic site license, which doesn't include that kind of support.
(Yes, we have a bunch of systems with additional support, but this "bug" doesn't
apply to them, they're still at rhel 2.1 or 3)
I thought this kind of thing was what the "enhancement" severity was for.