FYI:
deadly.org, aka openbsd journal, has a note from theo himself that ipf has
been removed from openbsd-current due to licensing changes (changes
committed at about 10 pm tuesday night).
2.9-release (which ships in two days) will have it, though. this affects
only -current.
i have not yet found out what code they will move to, or if they will fork
ipf. [i am not interested in speculating, i'm waiting for official word.]
this (obviously) really sucks. it should be possible to track some major
security changes in 2.9-release from -current and maintain ipf in there,
but not for long, and certainly not major features (ie 802.1q additions).
note also that ipf so far can be put back into the kernel just fine by
you, you're allowed to do that and the code merges in pretty nicely for
the most part.
blargh, however. please see deadly.org for the openbsd situation, notes
from theo and darren, and various flames and speculation. (its probably
not appropriate here.)
this obviously affects those of us who use openbsd and ipf as firewalls.
____________________________
jose nazario [EMAIL PROTECTED]
PGP: 89 B0 81 DA 5B FD 7E 00 99 C3 B2 CD 48 A0 07 80
PGP key ID 0xFD37F4E5 (pgp.mit.edu)
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
