From: Matthieu Baerts <matttbe@kernel.org>
To: "Mikhail Ivanov" <ivanov.mikhail1@huawei-partners.com>,
"Mickaël Salaün" <mic@digikod.net>
Cc: gnoack@google.com, willemdebruijn.kernel@gmail.com,
matthieu@buffet.re, linux-security-module@vger.kernel.org,
netdev@vger.kernel.org, netfilter-devel@vger.kernel.org,
yusongping@huawei.com, artem.kuzin@huawei.com,
konstantin.meskhidze@huawei.com,
MPTCP Linux <mptcp@lists.linux.dev>,
linux-nfs@vger.kernel.org, Paul Moore <paul@paul-moore.com>
Subject: Re: [RFC PATCH v2 1/8] landlock: Fix non-TCP sockets restriction
Date: Wed, 29 Jan 2025 12:57:54 +0100 [thread overview]
Message-ID: <69612036-8223-4f13-adf4-e247f9dd1f23@kernel.org> (raw)
In-Reply-To: <b9823ff1-2f66-3992-b389-b8e631ec03ba@huawei-partners.com>
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.
next prev parent reply other threads:[~2025-01-29 11:58 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-17 11:04 [RFC PATCH v2 0/8] Fix non-TCP restriction and inconsistency of TCP errors Mikhail Ivanov
2024-10-17 11:04 ` [RFC PATCH v2 1/8] landlock: Fix non-TCP sockets restriction Mikhail Ivanov
2024-10-17 12:59 ` Matthieu Baerts
2024-10-18 18:08 ` Mickaël Salaün
2024-10-31 16:21 ` Mikhail Ivanov
2024-11-08 17:16 ` David Laight
2024-12-04 19:29 ` Mickaël Salaün
2024-12-12 18:43 ` Mickaël Salaün
2024-12-13 18:19 ` Mikhail Ivanov
2025-01-24 15:02 ` Mickaël Salaün
2025-01-27 12:40 ` Mikhail Ivanov
2025-01-27 19:48 ` Mickaël Salaün
2025-01-28 10:56 ` Mikhail Ivanov
2025-01-28 18:14 ` Matthieu Baerts
2025-01-29 9:52 ` Mikhail Ivanov
2025-01-29 10:25 ` Matthieu Baerts
2025-01-29 11:02 ` Mikhail Ivanov
2025-01-29 11:33 ` Matthieu Baerts
2025-01-29 11:47 ` Mikhail Ivanov
2025-01-29 11:57 ` Matthieu Baerts [this message]
2025-01-29 14:51 ` Mickaël Salaün
2025-01-29 15:44 ` Matthieu Baerts
2025-01-30 9:51 ` Mickaël Salaün
2025-01-30 10:18 ` Matthieu Baerts
2025-01-31 11:04 ` Mikhail Ivanov
2024-12-04 19:27 ` Mickaël Salaün
2024-12-04 19:35 ` Mickaël Salaün
2024-12-09 10:19 ` Mikhail Ivanov
2024-12-10 18:04 ` Mickaël Salaün
2024-12-10 18:05 ` Mickaël Salaün
2024-12-11 15:24 ` Mikhail Ivanov
2024-12-12 18:43 ` Mickaël Salaün
2024-12-13 11:42 ` Mikhail Ivanov
2024-12-04 19:30 ` Mickaël Salaün
2024-12-09 10:19 ` Mikhail Ivanov
2024-10-17 11:04 ` [RFC PATCH v2 2/8] landlock: Make network stack layer checks explicit for each TCP action Mikhail Ivanov
2024-10-17 11:04 ` [RFC PATCH v2 3/8] landlock: Fix inconsistency of errors for TCP actions Mikhail Ivanov
2024-10-17 11:34 ` Mikhail Ivanov
2024-10-17 12:48 ` Tetsuo Handa
2024-11-06 9:27 ` Mikhail Ivanov
2024-12-04 19:32 ` Mickaël Salaün
2024-10-17 11:04 ` [RFC PATCH v2 4/8] selftests/landlock: Test TCP accesses with protocol=IPPROTO_TCP Mikhail Ivanov
2024-10-17 11:04 ` [RFC PATCH v2 5/8] selftests/landlock: Test that MPTCP actions are not restricted Mikhail Ivanov
2024-10-17 11:04 ` [RFC PATCH v2 6/8] selftests/landlock: Test consistency of errors for TCP actions Mikhail Ivanov
2024-12-10 18:07 ` Mickaël Salaün
2024-12-11 15:29 ` Mikhail Ivanov
2024-10-17 11:04 ` [RFC PATCH v2 7/8] landlock: Add note about errors consistency in documentation Mikhail Ivanov
2024-12-10 18:08 ` Mickaël Salaün
2024-12-11 15:30 ` Mikhail Ivanov
2024-10-17 11:04 ` [RFC PATCH v2 8/8] selftests/landlock: Test that SCTP actions are not restricted Mikhail Ivanov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=69612036-8223-4f13-adf4-e247f9dd1f23@kernel.org \
--to=matttbe@kernel.org \
--cc=artem.kuzin@huawei.com \
--cc=gnoack@google.com \
--cc=ivanov.mikhail1@huawei-partners.com \
--cc=konstantin.meskhidze@huawei.com \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=matthieu@buffet.re \
--cc=mic@digikod.net \
--cc=mptcp@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=willemdebruijn.kernel@gmail.com \
--cc=yusongping@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).