netdev - Re: [tproxy] udp + tproxy

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: <alpine.LNX.1.10.0811130815300.8076@fbirervta.pbzchgretzou.qr>
Date:	Thu, 13 Nov 2008 08:17:14 +0100 (CET)
From:	Jan Engelhardt <jengelh@...ozas.de>
To:	Balazs Scheidler <bazsi@...abit.hu>
cc:	KOVACS Krisztian <hidden@....bme.hu>,
	Andrey Luzgin <andrey@...msw.com>, tproxy@...ts.balabit.hu,
	netfilter-devel@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [tproxy] udp + tproxy


On Wednesday 2008-11-12 20:27, Balazs Scheidler wrote:
>> 
>> Since tproxy 4 (unlike tproxy 2) doesn't modify the incoming packets in
>> any way you should be able to get the correct destination address by
>> simply calling recvfrom() and using the source address returned by the
>> kernel.
>
>This is not true, recvfrom() returns the client address and does not
>return the original destination.

Mh, perhaps getsockname() could do something - well, at least
if used with accept() and as such, mostly for TCP only.
--
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