netdev - Re: [PATCH v2] net: introduce ip_local_unbindable

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] [day] [month] [year] [list]

Message-ID: <0101016ef1035a6a-d3a8b345-600a-4e28-b3da-12fd2fac72d1-000000@us-west-2.amazonses.com>
Date:   Tue, 10 Dec 2019 18:12:39 +0000
From:   subashab@...eaurora.org
To:     Jakub Kicinski <jakub.kicinski@...ronome.com>
Cc:     Maciej Żenczykowski <zenczykowski@...il.com>,
        "David S . Miller" <davem@...emloft.net>,
        Linux Network Development Mailing List 
        <netdev@...r.kernel.org>,
        Marcelo Ricardo Leitner <marcelo.leitner@...il.com>,
        Sean Tranchetti <stranche@...eaurora.org>,
        Eric Dumazet <edumazet@...gle.com>,
        Linux SCTP <linux-sctp@...r.kernel.org>
Subject: Re: [PATCH v2] net: introduce ip_local_unbindable_ports sysctl

> It's a form of one, agreed, although let's be honest - someone reading
> the transparent proxy use case in the commit message will not think of
> a complex AP scenario, but rather of a locally configured transparent
> proxy with IPtables or sockets or such.

Transparent proxy could be implemented using eBPF + XDP and those don't
need sockets. However, in that case we do need to block those specific 
ports
to avoid messing with unrelated traffic.