Comment 13 for bug 42759

Revision history for this message
Mossroy (mossroy) wrote :

I faced the same problem on my Ubuntu Edgy.

It has been a very serious issue for me, because I thought I was protected by Firestarter. After installing Network Manager, it appears I wasn't at all.
I have several services (samba shares, ssh, vnc etc) that are supposed to be accessible only by my local network. Those services have been accessible by anyone for almost one month, until I found the problem.

I had to slightly modify the solution in the link above. The command-line "source" doesn't exist on my computer (seems like that depends on which shell is used), so I replaced it with the ". " command.

So I created a file 50firestarter with the following content, and gave it the execution rights (sudo chmod +x 50firestarter)

#!/bin/sh

. /etc/firestarter/configuration 2>&1

# Check to see if the interface that changed is the one currently
# protected by firestarter. If not, quit.
[ "$1" != "$IF" ] && exit

# Check the current status of Firestarter
[ -e /var/lock/subsys/firestarter -o -e /var/lock/firestarter ]
fs_status=$?

case "$2" in
        up)
                [ "$fs_status" -gt 0 ] && /etc/init.d/firestarter start
        ;;
        down)
                ## Uncomment the following line to allow this script to
                ## turn off the firewall when the interface goes down.
                #[ "$fs_status" -eq 0 ] && /etc/init.d/firestarter stop
        ;;
esac