cvs commit: src/sys/contrib/pf/net if_pflog.c if_pflog.h
if_pfsync.c if_pfsync.h pf.c pf_ioctl.c pf_norm.c pf_osfp.c
pf_table.c pfvar.h src/sys/contrib/pf/netinet in4_cksum.c
sgk at troutmask.apl.washington.edu
Thu Feb 26 10:03:57 PST 2004
On Thu, Feb 26, 2004 at 09:46:55AM -0600, Jacques A. Vidrine wrote:
> [Disclaimer: I am long-time, loyal IPFilter user and I think everything
> else is crap. :-) ]
> On Wed, Feb 25, 2004 at 10:01:26PM -0800, Steve Kargl wrote:
> > Was this import discussed on arch@ or current@? We now have ipfw, ipfilter,
> > and pf in the base system. How many more firewall packages are we going
> > to import into the base system? Are you going to remove ipfw or ipfilter?
> > Is there a NO_PF make.conf knob?
> Choice is good. Three firewalls is maybe pushing the limit, but these
> three are Very Important to our community.
ports/security/pf gave you choice. This is a danger slope (ie.,
what about postfix, exim, bash, and ksh?).
> NO_PF, NO_IPF, and NO_IPFW would be good--- anyone have tested patches?
> The only downside IMHO is now I have to watch for security issues
> in pf :-)
A thankless job no doubt. So, THANK YOU!
More information about the cvs-all