root/fwsnort/tags/fwsnort-1.0.4/ChangeLog

Revision 427, 15.0 kB (checked in by mbr, 1 year ago)

updated release date for 1.0.4

  • Property svn:eol-style set to native
  • Property svn:keywords set to Author Date Id Revision
Line 
1 fwsnort-1.0.4 (01/22/2008):
2     - (Grant Ferley) Submitted patch to exclude loopback interfaces from
3       iptables allow rules parsing.  This behavior can be reversed with the
4       existing --no-exclude-loopback command line argument.
5     - (Grant Ferley) Submitted patch to IPTables::Parse to take into account
6       iptables policy output that contains "0" instead of "all" to represent
7       any protocol.
8     - (Grant Ferley) Submitted patch to IPTables::Parse to set sport and dport
9       to '0:0' if the protocol is 'all'.
10     - Bugfix to allow negated networks to be specified within iptables allow
11       rules or within the fwsnort.conf file.
12     - Updated install.pl to set the LC_ALL environmental variable to "C". This
13       should fix potential locale problems (this fix was borrowed from the
14       fwknop project).
15
16 fwsnort-1.0.3 (11/22/2007):
17     - Added --include-re-caseless and --exclude-re-caseless options to have
18       --include-regex and --exclude-regex options match case insensitively.
19     - Major signature update from Bleeding Threats. This update includes a
20       large number of new signatures with PCRE statements, with an emphasis on
21       detecting SQL injection attacks directed at internal webservers from
22       external sources.
23     - Added the ability to interpret PCRE statements that include simple
24       string matches separated by ".*" and ".+" as multiple iptables string
25       matches. The only negative consequence in terms of signature detection
26       is that ordering is not preserved; that is, the PCRE "/UNION.+SELECT/"
27       would only match a packet that contains "UNION" followed by "SELECT",
28       whereas an iptables rule that uses a string match for UNION and a
29       separate string match for SELECT would match a packet that contains both
30       strings but in reverse. Typically this is not a huge concern, and the
31       PCRE translation can be disabled with a new option --no-pcre.
32     - Added asn1 keyword to unsupported list.
33
34 fwsnort-1.0.2 (08/26/2007):
35     - Bugfix to make sure to add in header lengths for depth and offset values
36       since the string match extension compares bytes from the start of the
37       data link header.
38
39 fwsnort-1.0.1 (08/26/2007):
40     - Bugfix for ipt_rule_test() function name.
41     - Added the ability to automatically resolve command paths if any commands
42       cannot be found at the locations specified in the fwsnort.conf file.
43
44 fwsnort-1.0 (04/19/2007):
45     - Major update to include support for the NFQUEUE and QUEUE targets with
46       new command line options --NFQUEUE and --QUEUE.  This changes the
47       default LOG target to the NFQUEUE or QUEUE targets instead, and at the
48       same time builds a parallel Snort rule set in the
49       /etc/fwsnort/snort_rules_queue directory.  Every Snort rule in this
50       directory has at least one "content" keyword, which fwsnort uses in the
51       resulting iptables policy.  This policy only sends those packets to
52       snort_inline via the NFQUEUE or QUEUE target that match a content field
53       within some Snort rule.  The end result is that snort_inline should run
54       faster because the vast majority of packets (which are not malicious)
55       are processed via the Linux kernel without ever having to be sent to
56       userspace for analysis.  There is a tradeoff here in terms of attack
57       detection; snort_inline does not receive all packets associated with a
58       stream, so it cannot detect attacks quite as effectively (snort_inline
59       does not have an opportunity to look at reassembled buffers).  However,
60       this trade off may be acceptable for large sites where performance is
61       more important.
62     - Bug fix to remove any existing jump rules from the built-in INPUT,
63       OUTPUT, and FORWARD chains before creating a new jump rules.  This
64       allows the fwsnort.sh script to be executed multiple times without
65       creating a new jump rule into the fwsnort chains for each execution.
66     - Added the -X command line argument to allow fwsnort to delete all of
67       the fwsnort chains; this emulates the iptables command line argument
68       of the same name.
69     - Minor output enhancements and bugfixes to give more insight into the
70       translation process.  For example, if fwsnort is run in --snort-sid
71       mode but is unable to translate the specified signatures, the user is
72       notified.  Also, any existing /etc/fwsnort/fwsnort.sh script is not
73       archived and erased until fwsnort is actually going to write a new one.
74     - Added sid values to iptables comment match string.
75     - Bugfix for iptables string match --from and --to values to skip past
76       packet headers.  This is an approximation until a new --payload option
77       can be added to the string match extension.
78     - Added a single iptables rule testing API internally within fwsnort;
79       this adds a measure of consistency and removes some duplicate code.
80     - Added fwsnort mailing list at SourceForge.
81
82 fwsnort-0.9.0 (03/22/2007):
83     - Added support for multiple content matches since this is supported by
84       iptables.  This made a 10% increase in the fwsnort translation rate -
85       about 60% of all Snort-2.3.3 rules can be translated now.
86     - Added emulation for distance and within from previous content match
87       based on --from and --to (string match extension) and the length of
88       the previous pattern.
89     - Added the ability to include the Snort "msg", "classtype", "reference",
90       "priority", and "rev" fields in each iptables rule with the comment
91       match.  This can be disabled with a new command line argument
92       --no-ipt-comments.  The fwsnort version is also included within this
93       string.
94     - Added the ability to include the iptables rule number for each rule in
95       the fwsnort chains.  This is useful to easily know which iptables rule
96       is being triggered by network traffic (so it can be disabled if
97       necessary).  This can be disabled with --no-ipt-rule-nums.
98     - Added the --include-regex and --exclude-regex command line arguments.
99       These arguments allow rules to be included/excluded based on a regular
100       expression supplied on the command line.
101     - Updated to include the original Snort rule as a comment within the
102       fwsnort.sh script without having to use --verbose.
103     - Bugfix to force install of IPTables::Parse since it had been updated in
104       the fwsnort-0.8.2 release.
105     - Changed the IGNORE_ADDR variable to WHITELIST since this name better
106       describes the actual function of this var.  Updated to allow multiple
107       WHITELIST lines.
108     - Added the BLACKLIST variable to allow a true blacklist to be
109       instantiated with either the DROP or REJECT targets.  The syntax for the
110       BLACKLIST variable is "BLACKLIST  <ip or network>  <target>", where
111       "target" is either "DROP" or "REJECT".
112     - Added -F and -L command line arguments to flush and list iptables rules.
113       This is similar to the iptables command line args of the same names.
114     - Bugfix to ensure that traffic directed into the INPUT or coming from the
115       OUTPUT chains is treated as going toward or originating from the
116       HOME_NET.  After all the HOME_NET variable may contain an internal
117       network but omit the IP assigned to an external interface on the
118       firewall.
119     - Added "--log-ip-options" and "--log-tcp-options" to fwsnort LOG rules by
120       default (in the generated fwsnort.sh script).  This can be disabled with
121       --no-log-ip-opts and --no-log-tcp-opts arguments on the fwsnort command
122       line.
123     - Added the ability to include --log-tcp-sequence to LOG rules in
124       fwsnort.sh with a new argument --ipt-log-tcp-seq on the fwsnort command
125       line.
126     - Updated to handle negative string matches with "--string ! <string>".
127     - Updated to output all unsupported options of the /var/log/fwsnort.log
128       file to assist in the development of addition keyword emulation.
129
130 fwsnort-0.8.2 (02/17/2007):
131     - Updated to newer IPTables::Parse module that uses the array of hash
132       references method of returning iptables policy data.
133     - Added --Dump-ipt and --Dump-snort rules to allow iptables policy and
134       Snort rules to be dumped to STDOUT.
135     - Added bleeding-all.rules file from http://www.bleedingsnort.com/
136     - Added patches/bm_goodshift_fix.patch patch file that fixes an
137       initialization bug in the Boyer-Moore text search implementation in the
138       kernel (linux-2.6.x/lib/ts_bm.c) which caused slightly repetitive
139       patterns to only match at specific offsets with the string match
140       extension.
141     - Bugfix to ensure that a depth cannot be less that an offset (these
142       translate to the --to and --from command line arguments to iptables).
143     - Bugfix to escape '$' chars in iptables search strings.
144     - Added cd_rpmbuilder to make it easy to automatically build RPM files of
145       fwsnort.
146     - Added support for the iptables OUTPUT chain.
147     - Added the ChangeLog.svn file so that all of the changed files and
148       corresponding svn commit messages can be viewed (this file is built from
149       release to release).
150
151 fwsnort-0.8.1 (11/11/2005):
152     - Updated to use the string match extension "--algo bm" argument if
153       fwsnort is being run on a 2.6.14 (or greater) kernel.
154     - Updated to handle the Snort "offset" and "depth" keywords via the
155       --from and --to options to the string match extension in the 2.6.14
156       kernel.
157     - Created RPM package of fwsnort.
158     - Minor man page updates.
159
160 fwsnort-0.8.0 (07/11/2005):
161     - Completely re-structured fwsnort w.r.t. how it creates Netfilter
162       chains.  There are no longer any per-interface chains (this
163       greatly simplifies the Netfilter chains).
164     - Added three new chains "FWSNORT_INPUT_ESTAB", "FWSNORT_OUTPUT_ESTAB"
165       and "FWSNORT_FORWARD_ESTAB" to which tcp connections in the
166       ESTABLISHED state are jumped.  This allows fwsnort to use the
167       Netfilter tcp connection tracking mechanism to ignore Stick and Snot
168       style attacks (similar to the flow:established Snort rule option).
169     - Added true variable resolution (i.e. HTTP_SERVERS -> HOME_NET -> any)
170       for the Snort rule header.  This directly emulates the behavior of
171       the Snort IDS.
172     - Added IP protocol support in the translation of the Snort rule
173       header.  The Snort rule translation rate is now at about 53% for
174       Snort-2.3.
175     - Bugfix for ipopts Snort option (several arguments are not supported
176       by the ipv4options extension).
177     - Better tests for Netfiler TTL, TOS, and ipv4options matches.
178     - Replaced IGNORE_IP and IGNORE_NET keywords with single IGNORE_ADDR
179       keywork in fwsnort.conf.
180     - Updated to correctly handle ICMP type and code rules (itype and
181       icode Snort options) via the "--icmp-types type/code" convention.
182     - Added support for emulating the dsize Snort option through the use
183       of the Netfilter length match.
184     - Changed --type argument to --include-types and added list support
185       so it accepts things like "chat,ddos".  Also added --exclude-types
186       command line argument.
187     - Added support for multiple sid's (as a comma separated list) in
188       --snort-sids argument.  Also added --exclude-sids argument to remove
189       a list of sids from translation.
190     - Added support for the replace Snort option (originally from the
191       Snort_inline project).  The requires the replace string patch.
192     - Added support for restricting jump rules to a list of interfaces
193       via the --restrict-intf argument.
194     - Added kernel patch to extend the maximum packet length that the
195       string match extension will attempt to search from 1024 bytes to
196       2048 bytes (requires a kernel re-compile of course).
197     - Added DRP and REJ strings to logging prefix if --ipt-drop or
198       --ipt-reject is specified.
199     - Added snortspoof.pl, which is a simple perl script that emulates
200       the Stick and Snot tools.
201
202 fwsnort-0.7.0 (06/05/2005):
203     - Added support for the Snort pass action by using the ACCEPT target.
204     - Added support for the Snort log action by using the ULOG target
205       (which can then log the packet via the pcap writer).
206     - Added support for all fwsnort alerts to be logged via the ULOG
207       target instead of the LOG target.
208     - Added support for the "resp" keyword to allow it to drive the
209       Netfilter argument to the REJECT target.
210     - Added "pcre" to the unsupported list... this knocks the fwsnort
211       translation rate down to about 50% for Snort-2.3 rules (pcre is
212       heavily utilized).
213     - Added "priority" and "rev" to comment lines.
214
215 fwsnort-0.6.5 (03/20/2005):
216     - Updated to not attempt to download Snort rules from snort.org
217       because the rules are no longer available for automatic downloads
218     - Changed the install.pl script and the --update-rules mode for
219       fwsnort to download the latest signature set from
220       http://www.bleedingsnort.com/.
221       (Snort.org is now offering pay-service around their rule sets).
222     - Added signature test for the "flowbits" keyword.
223
224 fwsnort-0.6.4 (12/18/2004):
225     - Updated to Snort-2.3 rules.  FWSnort can convert a total of 1710
226       out of 2559 total Snort-2.3 rules.
227     - Updated to new Snort rules download link for --update-rules mode:
228       http://www.snort.org/dl/rules/snortrules-snapshot-CURRENT.tar.gz
229     - Updated to standard [+], [-], and [*] prefixes for info, warning
230       and die logging messages.
231     - Added --replace-string patches.
232
233 fwsnort-0.6.3 (04/04/2004):
234     - Added ignore functionality for both IPs and networks
235     - Split --ipt-block into --ipt-drop and --ipt-reject to add DROP
236       or REJECT rules respectively.
237     - Added --add-deleted option to allow rules in the "deleted.rules"
238       file to be added.
239
240 fwsnort-0.6.2 (03/19/2004):
241     - Added --internal-net and --dmz-net options so that internal and
242       dmz networks can be manually specified without having to parse
243       the output of ifconfig.  This is most useful for running fwsnort
244       on a linux system that is acting as a bridge where no ip addresses
245       are assigned to the interfaces.
246     - Bugfix for missing icmp-port-unreachable rejects for UDP packets.
247
248 fwsnort-0.6.1 (02/01/2004):
249     - Bugfix for not adding dmz interface rules to INPUT chain.
250     - Bugfix for not getting the DMZ interface network.
251
252 fwsnort-0.6 (01/04/2004):
253     - Speed increase and disk access decrease by writing iptables
254       commands to the iptables script only after all lines have been
255       generated.
256     - Bugfix for DMZ interface.
257     - Bugfix for multiple ip_proto fields.
258     - Removed the ip protocol as an allowed protocol for translation.
259     - Bugfix for negated port numbers.
260     - Removed "<-" rule direction since not even snort supports this.
261     - Fixed snort rule updates from snort.org.
262
263 fwsnort-0.5 (12/21/2003):
264     - Added "-j REJECT --reject-with tcp-reset" for tcp sessions
265       if the --ipt-block option is specified.
266     - Added ability to download latest snort rules from snort.org.
267     - Added --no-ipt-jumps.
268     - Added better checking for iptables build characteristics such
269       as the LOG target and wether or not the ipv4options extension
270       is compiled in.
271     - Added config preservation code from psad in install.pl.
Note: See TracBrowser for help on using the browser.