Tags: patch
I've determined that this bug happens because Firestater locks the entire
firewall including localhost.
In some configurations (notably Ubuntu Hardy) this blocks an esound event
generated by firestarter itself.
I've generated a patch which allows such traffic through localhost while
Firestarter is locked which allows Firestarter to unlock itself.
See https://bugs.launchpad.net/ubuntu/+source/firestarter/+bug/184017 for
more detail.
In a perfect, future, world it may be possible to configure Firestarter's
locked state from the GUI.
--- scriptwriter.c.org 2005-01-30 01:32:08.000000000 +1300
+++ scriptwriter.c 2008-06-21 05:29:35.000000000 +1200
@@ -229,11 +229,13 @@
fprintf (f, "# Lock the firewall, blocking all traffic\n"
"lock_firewall () {\n"
+ " $IPT -F;\n"
+ " $IPT -X\n"
+ " $IPT -A INPUT -i lo -s 127.0.0.1 -d 127.0.0.1 -j ACCEPT\n"
+ " $IPT -A OUTPUT -s 127.0.0.1 -d 127.0.0.1 -j ACCEPT\n"
" $IPT -P INPUT DROP\n"
" $IPT -P FORWARD DROP\n"
" $IPT -P OUTPUT DROP\n"
- " $IPT -F;\n"
- " $IPT -X\n"
" $IPT -Z\n"
" retval=$?\n"
" if [ $? -eq 0 ]; then\n"
