Overview
Request 282633 accepted
- Update to version 4.6.6.1 For more details see changelog.txt and
releasenotes.txt
* Previously the SAVE and RESTORE actions were erroneously disallowed
in the INPUT chain within the mangle file.
* The manpage descriptions of the mangle SAVE and RESTORE actions
incorrectly required a slash (/) prior to the mask value.
* Race conditions could previously occur between the 'start'
command and the 'enable' and 'disable' commands.
* The 'update' command incorrectly added the INLINE_MATCHES
option to shorewall.conf with a default value of 'Yes'. This
caused 'start' to fail with invalid iptables rules when the
alternate input format using ';' is used.
* Previously the LOCKFILE setting was not propagated to the
generated script. So when the script was run directly, the script
unconditionally used ${VARDIR}/lock.
- Created by toganm
- In state accepted
- Package maintainers: bruno_friedmann and polslinux
Request History
toganm created request
- Update to version 4.6.6.1 For more details see changelog.txt and
releasenotes.txt
* Previously the SAVE and RESTORE actions were erroneously disallowed
in the INPUT chain within the mangle file.
* The manpage descriptions of the mangle SAVE and RESTORE actions
incorrectly required a slash (/) prior to the mask value.
* Race conditions could previously occur between the 'start'
command and the 'enable' and 'disable' commands.
* The 'update' command incorrectly added the INLINE_MATCHES
option to shorewall.conf with a default value of 'Yes'. This
caused 'start' to fail with invalid iptables rules when the
alternate input format using ';' is used.
* Previously the LOCKFILE setting was not propagated to the
generated script. So when the script was run directly, the script
unconditionally used ${VARDIR}/lock.
toganm accepted request
reviewed OK