| Summary: | CUPS performs reverse DNS lookups even "HostNameLookups off" is set | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Robert Scheck <redhat-bugzilla> |
| Component: | cups | Assignee: | Zdenek Dohnal <zdohnal> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | qe-baseos-daemons |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | 7.2 | CC: | fweimer, jpopelka, mdshaikh, psklenar, redhat-bugzilla, thozza, zdohnal |
| Target Milestone: | rc | ||
| Target Release: | 7.4 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-03-27 16:20:05 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Bug Depends On: | |||
| Bug Blocks: | 1298243, 1380362, 1393869 | ||
|
Description
Robert Scheck
2016-04-10 17:48:37 UTC
Cross-filed case 01614836 on the Red Hat customer portal. Bug #1325692 comment #3 also applies here, too. With the same questions. Hi Robert, I managed to reproduce this issue, I will look into why it does reverse dns lookup. This:
sendmmsg(22, {{{msg_name(0)=NULL, msg_iov(1)=[{"4\354\1\0\0\1\0\0\0\0\0\0\3[v1\21fd3b:d910:cd43::2]\0\0\1\0\1", 39}], msg_controllen=0, msg_flags=0}, 39}, {{msg_name(0)=NULL, msg_iov(1)=[{"l^\1\0\0\1\0\0\0\0\0\0\3[v1\21fd3b:d910:cd43::2]\0\0\34\0\1", 39}], msg_controllen=0, msg_flags=MSG_WAITALL|MSG_SYN|MSG_RST|MSG_ERRQUEUE|MSG_WAITFORONE|MSG_CMSG_CLOEXEC|0x861c0010}, 39}}, 2, MSG_NOSIGNAL) = 2
is a *forward* DNS lookup for a syntactically invalid DNS name, something like:
[v1.fd3b:d910:cd43::2]
although the length field for the second label is off by one, along with the overall packet length (17 vs 18, 39 vs 40). I assume this corruption is due to your obfuscation attempt.
Something within CUPS calls getaddrinfo on this name, for the AF_UNSPEC family (because the above is a parallel A/AAAA query). This could be the result of a CUPS misconfiguration.
The CUPS configuration is mentioned at bug #1324662 comment #0. And the fd3b:d910:cd43::2 is the client IP address connecting to fd3b:d910:cd43::3, which is the CUPS server. And yes, I didn't pay attention if the changed IPv6 address has the same length - sorry. After clean installation of RHEL-7.3 situation totally reversed. This bug now seems it is not no longer in RHEL-7.3, but bug #1325692 appeared. Robert, would you mind testing if these bugs are still in RHEL-7.3? Yes, I will retest this based on RHEL 7.3. |