a b c d e f g h i j k l m n o p q r s t u v w x y z

diff from 28246 and 2409

Description: maintain and setup complicated firewall rules
 ferm is a frontend for iptables. It reads the rules from a
 structured configuration file and calls iptables(8) to insert them
 into the running kernel.
 .
 ferm's goal is to make firewall rules easy to write and easy to
 read. It tries to reduce the tedious task of writing down rules, thus
 enabling the firewall administrator to spend more time on developing
 good rules than the proper implementation of the rule.
 .
 To achieve this, ferm uses a simple but powerful configuration
 language, which allows variables, functions, arrays, blocks. It also
 allows you to include other files, allowing you to create libraries
 of commonly used structures and functions.
 .
 ferm, pronounced "firm", stands for "For Easy Rule Making".
Description: maintain and setup complicated firewall rules
 ferm allows one to reduce the tedious task of carefully inserting
 rules and chains by a large factor, thus enabling the firewall
 administrator to spend more time on developing good rules
 then the proper implementation of the rule.
 .
 ferm supports ipchains firewalls, ipfwadm rules and
 iptables firewalls. Changing to another system will be
 very easy, and ferm will help in the process.
 .
 ferm compiles ready to go firewall-rules from a structured rule-
 setup. These rules will be executed by the preferred kernel
 interface, such as ipchains(8) and iptables(8).
 .
 ferm will also add in modularizing firewalls, because it creates
 the possibility to split up the firewall into several different
 files, which can be reloaded at will, so you can dynamically
 adjust your rules.
 .
 ferm, pronounced "firm", stands for "For Easy Rule Making".
--- 28246	Thu Jan  1 00:00:00 1970
+++ 2409	Thu Jan  1 00:00:00 1970
@@ -1,16 +1,20 @@
 maintain and setup complicated firewall rules
- ferm is a frontend for iptables. It reads the rules from a
- structured configuration file and calls iptables(8) to insert them
- into the running kernel.
+ ferm allows one to reduce the tedious task of carefully inserting
+ rules and chains by a large factor, thus enabling the firewall
+ administrator to spend more time on developing good rules
+ then the proper implementation of the rule.
  .
- ferm's goal is to make firewall rules easy to write and easy to
- read. It tries to reduce the tedious task of writing down rules, thus
- enabling the firewall administrator to spend more time on developing
- good rules than the proper implementation of the rule.
+ ferm supports ipchains firewalls, ipfwadm rules and
+ iptables firewalls. Changing to another system will be
+ very easy, and ferm will help in the process.
  .
- To achieve this, ferm uses a simple but powerful configuration
- language, which allows variables, functions, arrays, blocks. It also
- allows you to include other files, allowing you to create libraries
- of commonly used structures and functions.
+ ferm compiles ready to go firewall-rules from a structured rule-
+ setup. These rules will be executed by the preferred kernel
+ interface, such as ipchains(8) and iptables(8).
+ .
+ ferm will also add in modularizing firewalls, because it creates
+ the possibility to split up the firewall into several different
+ files, which can be reloaded at will, so you can dynamically
+ adjust your rules.
  .
  ferm, pronounced "firm", stands for "For Easy Rule Making".