Bug 18169
Summary: | ipchains starts before network | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Seth Heckard <sheckard> |
Component: | ipchains | Assignee: | Cristian Gafton <gafton> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.0 | CC: | dr |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2000-10-03 17:47:57 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
Seth Heckard
2000-10-03 02:56:44 UTC
ipchains are supposed to start before the network - so you have NO time of a potential break-in occuring (ie: the time b/t the network coming up and ipchains being setup) this is normal on ALL Systems - if you're putting domain names in your ipchains then you've made a mistake and need to re-think configuring them. Seth is correct; setting up firewall rules after network interfaces come up (or more importantly, after network services begin to be started) creates a small window of opportunity which shouldn't exist. |