mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: John Johansen <john.johansen@canonical.com>
To: Paul Moore <paul@paul-moore.com>,
	Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
	Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-security-module@vger.kernel.org
Subject: Re: [GIT PULL] tomoyo update for v6.12
Date: Wed, 2 Oct 2024 19:33:40 -0700	[thread overview]
Message-ID: <f930e51e-3eb9-4146-a68c-1f226304cc86@canonical.com> (raw)
In-Reply-To: <CAHC9VhS_8JtU0KQyy3rEGt0CQ_XMQFt2Kic-bz-Qd=SMjeWe4Q@mail.gmail.com>

On 10/1/24 11:22, Paul Moore wrote:
> On Tue, Oct 1, 2024 at 12:36 PM Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
>> On Tue, 1 Oct 2024 at 07:00, Paul Moore <paul@paul-moore.com> wrote:
>>>
>>> Linus, it's unclear if you're still following this thread after the
>>> pull, but can you provide a little insight on your thoughts here?
> 
> ...
> 
>> If the consensus is that we should revert, I'll happily revert.
> 
> Starting tomorrow when I'm reliably back in front of computer I'll
> sort this out with the rest of the LSM folks.  Unless something
> unexpected comes up in the discussion I'll send you a revert later
> this week.
> 
I agree that this is the wrong approach and will add that it is
egregious enough that Ubuntu is going to have to disable Tomoyo as
it effectively allows by-passing signed module loads.

you can add my
Acked-by: John Johansen <john.johansen@canonical.com>

>> This
>> was all inside of the tomoyo subdirectory, so I didn't see it as some
>> kind of sidestepping, and treated the pull request as a regular
>> "another odd security subsystem update".
> 
> Yes, that's fair, I think you would need a deeper understanding of the
> LSM framework as well as an understanding of recent discussions on the
> list to appreciate all of the details.
> 


  parent reply	other threads:[~2024-10-03  2:33 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-27 10:43 Tetsuo Handa
2024-09-27 20:00 ` pr-tracker-bot
2024-09-28 13:54 ` Jonathan Corbet
2024-09-28 15:32   ` Tetsuo Handa
2024-10-02 14:51     ` Jonathan Corbet
2024-10-03  7:50     ` Christoph Hellwig
2024-10-01 14:00   ` Paul Moore
2024-10-01 16:36     ` Linus Torvalds
2024-10-01 18:22       ` Paul Moore
2024-10-02  3:31         ` Tetsuo Handa
2024-10-02 14:01           ` Paul Moore
2024-10-02 23:09             ` Tetsuo Handa
2024-10-02 23:50               ` Tetsuo Handa
2024-10-03  2:45               ` John Johansen
2024-10-03  4:26                 ` Tetsuo Handa
2024-10-03  5:35                   ` John Johansen
2024-10-03  6:16                     ` Tetsuo Handa
2024-10-03 12:59                       ` Tetsuo Handa
2024-10-05  4:06                         ` John Johansen
2024-10-05  3:59                       ` John Johansen
2024-10-03 15:39                     ` Dr. Greg
2024-10-05  4:24                       ` John Johansen
2024-10-03  2:33         ` John Johansen [this message]
2024-10-02 10:38       ` Dr. Greg
2024-10-02 14:35         ` Paul Moore
2024-10-03  2:24           ` John Johansen
2024-10-08 11:14           ` Dr. Greg
2024-10-08 18:25             ` Casey Schaufler
2024-10-11 17:06               ` Dr. Greg
2024-10-11 18:01                 ` Casey Schaufler
2024-10-03  2:27         ` John Johansen
2024-10-03 15:43           ` Dr. Greg
2024-10-05  4:37             ` John Johansen
2024-10-04 18:40           ` Dr. Greg
2024-10-04 18:58             ` Paul Moore
2024-10-05  2:33               ` Dr. Greg
2024-10-05 16:21                 ` Paul Moore
2024-10-07 11:21                   ` Dr. Greg
2024-10-07 13:28                     ` Paul Moore

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=f930e51e-3eb9-4146-a68c-1f226304cc86@canonical.com \
    --to=john.johansen@canonical.com \
    --cc=corbet@lwn.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=paul@paul-moore.com \
    --cc=penguin-kernel@i-love.sakura.ne.jp \
    --cc=torvalds@linux-foundation.org \
    /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

all inboxes | Powered by JetHome®