root/fwsnort/tags/fwsnort-1.0.6/ChangeLog

Revision 504, 19.0 KB (checked in by mbr, 15 months ago)

added blurb about the fwsnort-nobuildreqs.spec file

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