linux-security-module.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Dr. Greg" <greg@enjellic.com>
To: Paul Moore <paul@paul-moore.com>
Cc: John Johansen <john.johansen@canonical.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	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: Fri, 4 Oct 2024 21:33:57 -0500	[thread overview]
Message-ID: <20241005023357.GA20577@wind.enjellic.com> (raw)
In-Reply-To: <CAHC9VhS0aeDB2GzxJPHN8_LDk59gT_RuRKwb26K+3SzX7SQ=3g@mail.gmail.com>

On Fri, Oct 04, 2024 at 02:58:57PM -0400, Paul Moore wrote:

Good evening, I hope the week has gone well for everyone.

> On Fri, Oct 4, 2024 at 2:40???PM Dr. Greg <greg@enjellic.com> wrote:
> > On Wed, Oct 02, 2024 at 07:27:47PM -0700, John Johansen wrote:
> > > On 10/2/24 03:38, Dr. Greg wrote:
> > > >On Tue, Oct 01, 2024 at 09:36:16AM -0700, Linus Torvalds wrote:
> > > >>On Tue, 1 Oct 2024 at 07:00, Paul Moore <paul@paul-moore.com> wrote:
> 
> ...
> 
> > The third problem to be addressed, and you acknowledge it above, is
> > that there needs to be a flexible pathway for security innovation on
> > Linux that doesn't require broad based consensus and yet doesn't
> > imperil the kernel.

> The new LSM guidelines are documented at the URL below (and
> available in the README.md file of any cloned LSM tree), the
> document is also linked from the MAINTAINERS file:
>
> https://github.com/LinuxSecurityModule/kernel/blob/main/README.md#new-lsm-guidelines
>
> The guidelines were developed last summer on the LSM mailing list
> with input and edits from a number of LSM developers.
>
> https://lore.kernel.org/linux-security-module/CAHC9VhRsxARUsFcJC-5zp9pX8LWbKQLE4vW+S6n-PMG5XJZtDA@mail.gmail.com

We are intimately familiar with those documents.

Our reference was to the need for a technical solution, not political
medicaments.

> paul-moore.com

Have a good weekend.

As always,
Dr. Greg

The Quixote Project - Flailing at the Travails of Cybersecurity
              https://github.com/Quixote-Project

  reply	other threads:[~2024-10-05  2:34 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <0c4b443a-9c72-4800-97e8-a3816b6a9ae2@I-love.SAKURA.ne.jp>
     [not found] ` <877cavdgsu.fsf@trenco.lwn.net>
2024-10-01 14:00   ` [GIT PULL] tomoyo update for v6.12 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
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 [this message]
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=20241005023357.GA20577@wind.enjellic.com \
    --to=greg@enjellic.com \
    --cc=corbet@lwn.net \
    --cc=john.johansen@canonical.com \
    --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;
as well as URLs for NNTP newsgroup(s).