ufw flushes iptables although disabled
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ufw |
Fix Released
|
Undecided
|
Jamie Strandboge | ||
0.16-hardy |
Fix Released
|
Undecided
|
Jamie Strandboge | ||
0.23-intrepid |
Fix Released
|
Undecided
|
Jamie Strandboge | ||
ufw (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Hardy |
Fix Released
|
Undecided
|
Jamie Strandboge | ||
Intrepid |
Fix Released
|
Undecided
|
Jamie Strandboge | ||
Jaunty |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
the init.d script for ufw flushes the iptables when called with "stop" even when ENABLED=no in the ufw.conf.
i noticed this when i did a "init 1" for some backups. after getting back to "init 5" there where still no rules, but all services are started of course.... so for me... this was a kind of a security problem, so ill report it as such. but its not THAT critical i guess...
i set my own iptables with ifupdown commands and network seems to stay enabled in "init 1".
you could argue, thats my own fault... but i did not even know about ufw.. and its disabled... so it shouldnt tinker with my iptables! :)
imho the init script should test if ENABLED is set, while stopping just like it is done in the start case:
if [ "$ENABLED" = "yes" ] || [ "$ENABLED" = "YES" ]; then
...
and not do anything if its disabled.
ufw 0.23.2
ubuntu 8.10
Changed in ufw: | |
assignee: | nobody → jdstrand |
assignee: | nobody → jdstrand |
Thank you for using ufw and taking the time to report a bug. I am working on a fix for this and it should be available soon.