Bug#690158: ettercap: unconditionally sets net.ipv4.ip_forward=0

2012-10-12 Thread Teodor MICU
2012/10/12 Simon Paillard spaill...@debian.org: On top of that, ettercap is designed for man in the middle attacks, disabling kernel forwarding seems to be a must. man ettercap: NAME ettercap - multipurpose sniffer/content filter for man in the middle attacks Ok, good to know.

Bug#690158: ettercap: unconditionally sets net.ipv4.ip_forward=0

2012-10-12 Thread Barak A. Pearlmutter
On top of that, ettercap is designed for man in the middle attacks, disabling kernel forwarding seems to be a must. Agreed, with one caveat: ettercap *is* capable of mounting a MTM attack by ARP poisoning, which works fine on a non-router host, in which case forwarding wouldn't be enabled in

Bug#690158: ettercap: unconditionally sets net.ipv4.ip_forward=0

2012-10-11 Thread Simon Paillard
Control: -1 severity wishlist On Wed, Oct 10, 2012 at 06:20:58PM +0300, Teodor wrote: Package: ettercap Version: 1:0.7.3-2.1 Severity: grave Justification: causes non-serious data loss I've just found that running 'ettercap' on gateway system (were ip_forward is a must) will

Bug#690158: ettercap: unconditionally sets net.ipv4.ip_forward=0

2012-10-10 Thread Teodor
Package: ettercap Version: 1:0.7.3-2.1 Severity: grave Justification: causes non-serious data loss Hi, I've just found that running 'ettercap' on gateway system (were ip_forward is a must) will unconditionally disable the kernel flag. This affects both Debian 6.0 (squeeze) and Debian 7.0