Bug 57659
Summary: | xinetd starts doing ident requests after service attack | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Daniel Senie <dts> |
Component: | xinetd | Assignee: | Jay Fenlason <fenlason> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Brock Organ <borgan> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.0 | CC: | jfeeney, kmaraas |
Target Milestone: | --- | Keywords: | Security |
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2003-04-23 13:14:13 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Daniel Senie
2001-12-18 14:28:46 UTC
Hmm... not having looked into it properly yet, you could disable USERID queries by firewalling traffic to port 113 from your system. It is possible to work around this problem with an IPCHAINS rule on OUTBOUND traffic, which does a REJECT (so that an ICMP packet goes back to xinetd). However this becomes more of an issue to manage, since it'll affect all applications, and that's not necessarily desirable. The underlying bug here is I don't have USERID turned on for the service. Should not be necessary to fool the thing if it's works as documented. True, I was just giving a tips for an immediate workaround. Appreciate the concern. Had it covered, but other folks may find the extra info useful if they see similar symptoms. Is this still the same? Red Hat Linux 7.0 is no longer supported and xinetd has been updated in newer distributions. Please reopen this bug if you see the problem still occur in Red Hat Linux 7.1 or later. |