On 2006/11/07 22:47, Martin Ferrari <[EMAIL PROTECTED]> wrote: > The manpage is incomplete about migration from previous versions of > ferm. Running my old ferm script, ferm said about option automod: > The 'option' keyword is deprecated
Thanks for pointing that out, I have added a notice about that in the new ferm manpage. It's all in the NEWS file, but it is indeed a good idea to mention that in the manpage, too. On 2006/11/11 10:19, Goetz Golla <[EMAIL PROTECTED]> wrote: > The ferm syntax seems to have changed drastically from sarge to > etch, with no automatic migration and no documentation about it. The > result is that in many cases the old rules will not load at all, > with many cryptic warnings like: "Warning in ferm.conf line 2: > Please declare the policy in a separate statement" The warnings are there to help you migrate to the new syntax, but the old configuration file should still work. ferm 1.2 is meant to be compatible with 1.1. Please create a new bug report with an example of a non-working configuration, so I can check that issue. > The big problem here is that as a result the server will be *open* > und completelly unprotected by any filter rules on the internet, and > with no easy way to get the filter rules back in (due to lack of > documentation). When anything fails, ferm automatically reverts all rules to the previous configuration. The same here: if you feel this rollback feature does not work, please open a new bug report. By the way, you might find "ferm --interactive" interesting. Max -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
