Contributed by jose on from the syntax-changes dept.
> remove the "flags X" syntax. > noone who wrote "flags S" meant that, but actually something like "flags > S/SA". with "flags S" changing its actual meaning as more flags got > supported, things got worse. > ok dhartmei@, pb@ (henning@)Hence, you'll have to use something like flags S/SAFRUPEW in your pf.conf files. The good news is you can use macros, though:
> Remove 'flags X' syntax, if people make heavy use of X/FOOBAR, they > chould use macros, e.g. > tcpinit="S/SAFR" > pass in ... flags $tcpinit (pb@)This was done to ensure the correctness of matches, and once you migrate your rulesets over you should be good. Thanks to Daniel for some information on this change.
(Comments are closed)
By Anonymous Coward () on
Comments
By Anonymous Coward () on
The trolls are out in full force this week.
Back! Back! Back into the darkness from which you came. Lest you be turned into stone by the light of my cruel logic.
By Shane () on
By Anonymous Coward () on
By zil0g () on
LOL
Comments
By Anonymous Coward () on
Comments
By Anonymous Coward () on
I contribute nothing more than my $40 stipend for the cds. I get a secure OS with that contains software that some company would have me paying 1000s of hard earned dollars. Sometimes I have complaints, nothing is perfect. But in my book, complaining is not contributing. So shall I say, I suffer in delightful silence, while you make a fool of yourself as a prime example of a non-contributing whiner.
Comments
By Pedro () on
i mean even when saying "something critical" there are certain quality standards to respect. And some people on this site dont seem to be able to even write "something critical" without failing miserable at respecting even the lowest of these standards.
By rankor () on
By Anonymous Coward () on
By Lars Hansson () on
Maybe you should go troll in the woods or did the big trolls not want to play with you?
By Anonymous Coward () on
Comments
By Anonymous Coward () on
By Noob () on
By Anonymous Coward () on
PF was written mainly as a program of opportunity due to the licensing issues of IPF and fallout between Theo and Reed. In fact, no one expected to be writing one until the issue was forced, mainly due to Reed's (rightful, however annoying) insistence on his license terms, OBSD's project goals (which you are not aware of fully despite it plainly displayed on their web page) and insistence of coding over carefully looking at licensing (their mistake, but they are coders, not lawyers), and the current legal environment, particularly surrounding copyright and the use of derivative works (occurs most stringently in the US, so your mileage may vary depending on where you reside).
Plus, it seems PF has had fewer security issues than IPF during a similar timeframe. Darn. There goes your tiny slice at fame. Good day.
By Anonymous Coward () on
Comments
By messersmidth () on
When you start to do submit sourcecode to the project often you might end up there yourself
Comments
By Anonymous Coward () on
By Jedi/Sector One () j@pureftpd.org on http://www.pureftpd.org/
Hmm, actually the reason of the change is that it was confusing, and that it was _not_ working the way people expected it to (it was working the way it was documented, but people misread the documentation...) .
Now, things are clear.
Comments
By Anonymous Coward () on
By Anonymous Coward () on
Thanks
Comments
By Anonymous Coward () on
For the rest nothing is changed iirc
Comments
By Anonymous Coward () on
No software addons (ie. 'features'). That's why it's called stable :)
By Rojareyn () cfuhrman at NO pobox SPAM dot com (you know what t on mailto:cfuhrman at NO pobox SPAM dot com (you know what t
You get the CVS commits for EVERYTHING (www, ports, src, etc).
Better still, subscribe to the digest version...