netdev - Re: [tproxy,regression] tproxy broken in 2.6.32

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20091128.132158.34557470.davem@davemloft.net>
Date:	Sat, 28 Nov 2009 13:21:58 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	hadi@...erus.ca
Cc:	hidden@....bme.hu, kaber@...sh.net, hidden@...abit.hu,
	aschultz@...p10.net, tproxy@...ts.balabit.hu,
	netdev@...r.kernel.org
Subject: Re: [tproxy,regression] tproxy broken in 2.6.32

From: jamal <hadi@...erus.ca>
Date: Sat, 28 Nov 2009 14:44:02 -0500

> On Sat, 2009-11-28 at 20:05 +0100, KOVACS Krisztian wrote:
>> Well, it depends whether or not you consider the initial setup valid.
>> 
> 
> Based on what i see - I frankly dont. If i looked up the source address

What matters is that this worked for years and we broke it.

There is no other valid discussion about this.

The only thing to "pick" right now is whether we revert the
thing completely or add a sysctl and default it to off.

I prefer the former because nobody is going to turn the thing
on, especially not distributions, and that's %99.9999 of users.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html