Bug#615176: firestarter: broken on 2.6.37

2011-03-01 Thread QuadCEM
On 02/28/2011 11:11 AM, Paul Cupis wrote: On 27/02/11 23:57, QuadCEM wrote: I have attached the iptables output; it seems to be setting rules, but iptables is still allowing all inbound traffic to connect to the machine (even non-established traffic). I think the ACCEPT all -- 0.0.0.0/0

Bug#615176: firestarter: broken on 2.6.37

2011-03-01 Thread Paul Cupis
On 01/03/11 09:53, QuadCEM wrote: I upgraded to firestarter 1.0.3-10 and to kernel 2.6.37-2 this afternoon and it seems to be back to normal now ... did you already release a fix for this, or did something in the kernel update take care of it? The -10 version doesn't do anything regarding what

Bug#615176: firestarter: broken on 2.6.37

2011-03-01 Thread QuadCEM
On 03/01/2011 10:59 AM, Paul Cupis wrote: On 01/03/11 09:53, QuadCEM wrote: I upgraded to firestarter 1.0.3-10 and to kernel 2.6.37-2 this afternoon and it seems to be back to normal now ... did you already release a fix for this, or did something in the kernel update take care of it? The

Bug#615176: firestarter: broken on 2.6.37

2011-02-28 Thread Paul Cupis
On 27/02/11 23:57, QuadCEM wrote: I have attached the iptables output; it seems to be setting rules, but iptables is still allowing all inbound traffic to connect to the machine (even non-established traffic). I think the ACCEPT all -- 0.0.0.0/00.0.0.0/0 is trumping all other

Bug#615176: firestarter: broken on 2.6.37

2011-02-27 Thread Paul Cupis
On 26/02/11 12:57, Charles Munson wrote: Actually I take that back ... the firewall doesn't appear to be working at all for incoming connections anymore. Even in restrictive mode connections to my services can still be made. Maybe the priority should be raised to critical rather than normal.

Bug#615176: firestarter: broken on 2.6.37

2011-02-27 Thread QuadCEM
On 02/27/2011 09:32 PM, Paul Cupis wrote: On 26/02/11 12:57, Charles Munson wrote: Actually I take that back ... the firewall doesn't appear to be working at all for incoming connections anymore. Even in restrictive mode connections to my services can still be made. Maybe the priority should

Bug#615176: firestarter: broken on 2.6.37

2011-02-26 Thread QuadCEM
Package: firestarter Version: 1.0.3-9 Severity: normal Tags: sid Firestarter does not show active connections on the new kernel, nor does it acknowledge the Drop silently preference. When Drop silently is chosen, the ports are still treated as closed (rather than stealthed). Tried uninstalling,

Bug#615176: firestarter: broken on 2.6.37

2011-02-26 Thread Charles Munson
Actually I take that back ... the firewall doesn't appear to be working at all for incoming connections anymore. Even in restrictive mode connections to my services can still be made. Maybe the priority should be raised to critical rather than normal.