[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <69612036-8223-4f13-adf4-e247f9dd1f23@kernel.org>
Date: Wed, 29 Jan 2025 12:57:54 +0100
From: Matthieu Baerts <matttbe@...nel.org>
To: Mikhail Ivanov <ivanov.mikhail1@...wei-partners.com>,
Mickaël Salaün <mic@...ikod.net>
Cc: gnoack@...gle.com, willemdebruijn.kernel@...il.com, matthieu@...fet.re,
linux-security-module@...r.kernel.org, netdev@...r.kernel.org,
netfilter-devel@...r.kernel.org, yusongping@...wei.com,
artem.kuzin@...wei.com, konstantin.meskhidze@...wei.com,
MPTCP Linux <mptcp@...ts.linux.dev>, linux-nfs@...r.kernel.org,
Paul Moore <paul@...l-moore.com>
Subject: Re: [RFC PATCH v2 1/8] landlock: Fix non-TCP sockets restriction
On 29/01/2025 12:47, Mikhail Ivanov wrote:
> On 1/29/2025 2:33 PM, Matthieu Baerts wrote:
>> So if TCP is blocked, MPTCP should be blocked as well. (And eventually
>> having the possibility to block only TCP but not MPTCP and the opposite,
>> but that's a different topic: a possible new feature, but not a bug-fix)
>
> What do you mean by the "bug fix"?
I mean that to me, adding the possibility to block one but not the other
might be seen as a new feature. But at the end, that's up to the
Landlocks maintainers to decide! So feel free to ignore this previous
comment :)
Cheers,
Matt
--
Sponsored by the NGI0 Core fund.
Powered by blists - more mailing lists