holm/shorewall_code
1
0
Fork 0
forked from extern/shorewall_code
Code Pull Requests Activity

Correct handling of NFQUEUE(queue-num) in a policy

Browse Source 
Signed-off-by: Tom Eastep <teastep@shorewall.net>
This commit is contained in:
Tom Eastep 2010-02-25 08:46:20 -08:00
parent 99ec099c98
commit db39402e75
4 changed files with 13 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Shorewall/Perl/Shorewall/Chains.pm
View File

@ -635,7 +635,7 @@ sub add_jump( $$$;$$$ ) {
#
# Ensure that we have the chain unless it is a builtin like 'ACCEPT'
#
$toref = ensure_chain( $fromref->{table} , $to ) unless $builtin_target{ $to };
$toref = ensure_chain( $fromref->{table} , $to ) unless $builtin_target{$to} || $to =~ / /; #If the target has options, it must be a builtin.
}
#

2
Shorewall/changelog.txt
View File

@ -2,6 +2,8 @@ Changes in Shorewall 4.4.7.6
1) Fix Debian init script exit status
2) Fix NFQUEUE(queue-num) in policy
Changes in Shorewall 4.4.7.5
1) Don't create a logging chain for rules with '-j RETURN'.

6
Shorewall/known_problems.txt
View File

@ -64,3 +64,9 @@
are 1/2 of the values given in the rule.
Corrected in 4.4.7.5.
9) If a queue-number is specified in an NFQUEUE policy (e.g.,
NFQUEUE(0)), invalid iptables-restore input is generated.
10) The Debian init scripts return exit status 0, even when the command
fails.

4
Shorewall/releasenotes.txt
View File

@ -191,6 +191,10 @@ Shorewall 4.4.7 Patch Release 6.
init script would still return a success (zero) exit status. It now
returns a failure status (1) when the command fails.
2) Previously, if a queue number was specified in an NFQUEUE policy
(e.g., NFQUEUE(0)), invalid iptables-restore input would be
generated.
----------------------------------------------------------------------------
P R O B L E M S C O R R E C T E D I N 4 . 4 . 7 . 5
----------------------------------------------------------------------------