netdev - Re: [PATCH RFC 0/4] net: add bpfilter

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: <20180219.103139.2230101523652161323.davem@davemloft.net>
Date:   Mon, 19 Feb 2018 10:31:39 -0500 (EST)
From:   David Miller <davem@...emloft.net>
To:     laforge@...monks.org
Cc:     fw@...len.de, daniel@...earbox.net, netdev@...r.kernel.org,
        netfilter-devel@...r.kernel.org, alexei.starovoitov@...il.com
Subject: Re: [PATCH RFC 0/4] net: add bpfilter

From: Harald Welte <laforge@...monks.org>
Date: Mon, 19 Feb 2018 16:27:46 +0100

> On Mon, Feb 19, 2018 at 10:13:35AM -0500, David Miller wrote:
> 
>> Florian, first of all, the whole "change the iptables binary" idea is
>> a non-starter.  For the many reasons I have described in the various
>> postings I have made today.
>> 
>> It is entirely impractical.
> 
> Why is it practical to replace your kernel but not practical to replace
> a small userspace tool running on top of it?

The container is just userspace components.  Those are really baked in
and are never changing.

The hosting element, on the other hand, can upgrade the kernel in that
scenerio no problem.

This is how cloud hosting environments work.