OpenBSD's PF Developers Interview 110
An anonymous reader writes "ONLamp.com has published a very long interview with 6 OpenBSD's PF developers: Cedric Berger (cedric@), Can Erkin Acar (canacar@), Daniel Hartmeier (dharmei@), Henning Brauer (henning@), Mike Frantzen (frantzen@) and Ryan McBride (mcbride@).
Start reading from the first half and continue with the second part."
Interview... BSD style (Score:5, Funny)
Just like BSD, its all done in parallel!
Re:Did they ask them... (Score:5, Informative)
pf.conf is cryptic? The manpage and demo files in
Re:Someone's gotta say it (Score:2)
If I were Ryan, I'd take to the hills before David Boies slaps him with a five billion dollar lawsuit
Re:Bah (Score:1, Offtopic)
Re:Bah (Score:2)
Re:Bah (Score:2, Funny)
Re:Bah (Score:1)
Re:So the world wants to know... (Score:4, Informative)
PF is the Packet Filter in OpenBSD, kind of similar to iptables/ipchains in Linux.
Re:So the world wants to know... (Score:1, Interesting)
Re:the Failure of *BSD (Score:1)
Dissemination is the goal (Score:5, Informative)
Spreading technology, not ideology...
Each time some BSD code is incorporated in a proprietary product the world is likely a better place, you don't want everyone and his dog coding an IP stack, if it was the case it would not be some unpatched windows boxes that would be used as attack launch points, the would be everything from your fridge to your car...
BTW the license does not discourage anything, it just does not make it mandatory. Common sense makes contributing back a good thing, as maintaining a fork is likely more expensive that contributing back your valuable intellectual property would cost you.
Re:the Failure of *BSD (Score:3, Insightful)
You disliking it was strongly implied, and then supported by you calling it a failure right now.
Of course, you believe that it is the `weak' license that made it a `failure', but you clearly do not understand the goals of project.
The Goal's of the BSD projects
Re:OpenBSD problems (Score:5, Interesting)
Quite the contrary, actually.
He has a project that's rock solid, and he doesn't want forks polluting OpenBSD's good reputation.
I don't see why that's a problem. After all, OpenBSD is _his_ baby, and it's his call what to do with it.
I'd probably do the same if I were in Theo's shoes.
Re:OpenBSD problems (Score:3, Interesting)
Re:OpenBSD problems (Score:2)
Sure, go ahead! That's what the MirBSD [bsdadvocacy.org] people did after all...
Re:OpenBSD problems (Score:4, Informative)
Re:OpenBSD problems (Score:1, Interesting)
In most cases, the fork should be named "BrokenBSD" by default.
Re:OpenBSD problems (Score:1)
It was a compliment to OpenBSD. If you mess with
it, you'll probably break it. Hence, some crack
pot trying to branch his own BSD release should
name it 'BrokenBSD'.
PF can Filers By OS (Score:5, Interesting)
It's great of VPN stuff - all of my VPN equipment is OpenBSD - so I just don't allow any packets from any other OS. This mitigates any attack - now my attacker has to have and OpenBSD computer (or at least spoof one)
Re:PF can Filers By OS (Score:1, Interesting)
Block external Windows clients? But I'm behind an OpenBSD firewall running pf myself, so connections from my Windows machine will look like OpenBSD. (synproxy
And what happens when Longhorn starts using a TCP/IP stack indistinguishable from OpenBSD? (not that that's likely...)
What are the chances of someone attacking (let along successfully) an OpenBSD machine from Windows anyway? More likely they're on Linux or so
Wow (Score:1, Interesting)
Re:Wow (Score:4, Insightful)
I read both pages, and.... (Score:1)
I did like that os filtering idea.
pf also available for FreeBSD (Score:5, Informative)
pf has been available in ports [freshports.org] for quite a while. Although it only works on the 5.x branch, I'm running it as my firewall on an old 166mhz Pentium.
Personally, I find FreeBSD easier to deal with, but that's just me.
FreeBSD has pf(4) support too (Score:2)
Re:Wow (Score:5, Interesting)
pf vs ipf vs ipfw vs iptables (Score:1)
also maybe add in some ebtables+iptables stuff as well
Re:pf vs ipf vs ipfw vs iptables (Score:5, Informative)
For an example of setting up firewall for home or small office [openbsd.org], have a look at the execellent PF User Guide> [openbsd.org].
Tired of sucky download performance when you max your upload on your ADSL connection? Well, PF solves that with packet queueing and prioritization [openbsd.org].
Re:pf vs ipf vs ipfw vs iptables (Score:4, Insightful)
Re:pf vs ipf vs ipfw vs iptables (Score:2, Interesting)
I love OpenBSD for firewall/vpn duties... now if they'd just hurry the hell up and implement NAT-t for isakmpd i'd be a happy camper...
AuthPF is neat too (Score:5, Informative)
Useful if you want to hide services from the outside world (except for selected users), but you don't want the complexity of ssh tunnels/vpn. (ie: I want to give some people access to my ftp server but hide it from the rest of the world, and not give them vpn access to the whole network)
It's impossible to create reliable BSD statistics! (Score:5, Informative)
So, what can XP users use... (Score:1)
Re:So, what can XP users use... (Score:2)