Overview
Request 124332 accepted
- Update to 4.5.5 For more details see changelog.txt and
releasnotes.txt
* This release includes all defect repair from Shorewall 4.5.4.1
and 4.5.4.2.
* The Shorewall compiler sometimes must defer generating a rule
until runtime. This is done by placing shell commands in its
internal representation of a chain. These commands are then
executed at run time to create the final rule.
If all of the following were true, then an incorrect ruleset
could be generated:
+ Optimization level 4 was set.
+ A chain (chain A) containing shell commands had three or
fewer rules and commands.
+ The last rule in a second chain was a conditional jump to
chain A.
Under these conditions, the rules and commands in Chain A
* The Shorewall-core configure and configure.pl script were
treating SYSCONFDIR as a synonym for CONFDIR making it
impossible to set SYSCONFDIR.
- Created by toganm
- In state accepted
- Package maintainers: bruno_friedmann and polslinux
Request History
toganm created request
- Update to 4.5.5 For more details see changelog.txt and
releasnotes.txt
* This release includes all defect repair from Shorewall 4.5.4.1
and 4.5.4.2.
* The Shorewall compiler sometimes must defer generating a rule
until runtime. This is done by placing shell commands in its
internal representation of a chain. These commands are then
executed at run time to create the final rule.
If all of the following were true, then an incorrect ruleset
could be generated:
+ Optimization level 4 was set.
+ A chain (chain A) containing shell commands had three or
fewer rules and commands.
+ The last rule in a second chain was a conditional jump to
chain A.
Under these conditions, the rules and commands in Chain A
* The Shorewall-core configure and configure.pl script were
treating SYSCONFDIR as a synonym for CONFDIR making it
impossible to set SYSCONFDIR.
toganm accepted request
reviewed ok.