2010-12-30 21:01:46 +01:00
|
|
|
1) On systems running Upstart, shorewall-init cannot reliably secure
|
2010-12-30 20:47:25 +01:00
|
|
|
the firewall before interfaces are brought up.
|
|
|
|
|
|
2011-04-14 02:22:07 +02:00
|
|
|
Corrected in Shorewall 4.4.19.1
|
|
|
|
|
|
|
|
|
|
2) There is a harmless duplicate ACCEPT rule in the INPUT filter chain
|
|
|
|
|
when the firewall is stopped.
|
|
|
|
|
|
|
|
|
|
Corrected in Shorewall 4.4.19.1
|
|
|
|
|
|
|
|
|
|
3) Shorewall interprets all 'nexthop' routes as default routes when
|
|
|
|
|
analyzing the pre-start routing configuration. This can lead to
|
|
|
|
|
unwanted default routes when the firewall was started or stopped.
|
|
|
|
|
|
|
|
|
|
Corrected in Shorewall 4.4.19.1
|
|
|
|
|
|
|
|
|
|
3) A defect introduced in Shorewall 4.4.17 broke the ability to
|
|
|
|
|
specify ':<low port>-<high port>' in the ADDRESS column of
|
|
|
|
|
/etc/shorewall/masq.
|
|
|
|
|
|
|
|
|
|
Corrected in Shorewall 4.4.19.1
|
|
|
|
|
|
