| Summary: | Add variables to rc.conf for rc.firewall | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Base System | Reporter: | sjr <sjr> | ||||||||
| Component: | conf | Assignee: | Crist J. Clark <cjc> | ||||||||
| Status: | Closed FIXED | ||||||||||
| Severity: | Affects Only Me | ||||||||||
| Priority: | Normal | ||||||||||
| Version: | 4.5-PRERELEASE | ||||||||||
| Hardware: | Any | ||||||||||
| OS: | Any | ||||||||||
| Attachments: |
|
||||||||||
|
Description
sjr
2002-01-04 18:10:01 UTC
Responsible Changed From-To: freebsd-bugs->cjc Firewalling and rc scripts? Sounds like a job for Crist! State Changed From-To: open->closed The rc.firewall scripts should not be used without local customizations. Encouraging their use unmodified by adding variables to rc.conf(5) is a step in the wrong direction. Ideally, I would subtly break rc.firewall so the rules would have to be changed, not just some variables set, for the firewall to work at all... but then I think about the noise on -questions that this would generate. |