Jose Nazario wrote:
> --- PURELY FYI --------
>
> note that openbsd dropped ipf last week, meaning releases past 2.9 wil not
> carry ipf.
Correct.
> this was due to some licensing changes by the ipf author darren
> reed,
Depending on who you read; Darren says it was a clarification, but the
result is the same.
> and their subsequent incompatability with the stated goals of the
> openbsd project. ipf, a great firewalling package, is still available on
> netbsd and freebsd.
Note that it will continue to be available on OpenBSD as well, just not
as part of the main release. You can still download, [modify if you
choose,] and run locally. You just can't distribute changes without
Darren's say-so, which is (I understand) the sticking point against the
OpenBSD license. I'm also under the impression that the OpenBSD ports
tree carries packages whose license may not necessarily be compatible
with the OpenBSD license (there certainly are GPL'ed packages in it), so
an appearance there is probably a fairly safe bet.
> sorry, just wanted to clarify for the completeness of the record. i am
> still an openbsd advocate, and wait to see what will be forthcoming as a
> packet filter in the kernel.
Can't comment on that, but the plan as of a few days ago called for a
port of ipfw from FreeBSD for the userland stuff. I seem to recall
something about changes to the kernel being unnecessary, but I could be
making that part up.
> several of us on this list constantly
> recommended openbsd/ipf as a great combination, i'm sorry it's no longer
> going to be available.
See above. Available, just not out of the box.
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
