linux-security-module.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Moore <paul@paul-moore.com>
To: linux-security-module@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: update the LSM entry
Date: Wed, 15 Nov 2023 23:36:49 -0500	[thread overview]
Message-ID: <CAHC9VhSjAvDPiUtisP8mNbdPwvi6-8uJUbgoRv0GzYZ5-c_qtg@mail.gmail.com> (raw)
In-Reply-To: <CAHC9VhToYWVTmXmmXMdGE3XZcBV65RrFWvFaYX+nWd-Mr6k=yA@mail.gmail.com>

On Wed, Nov 15, 2023 at 12:21 PM Paul Moore <paul@paul-moore.com> wrote:
> On Wed, Nov 15, 2023 at 11:48 AM Paul Moore <paul@paul-moore.com> wrote:
> >
> > Bring the LSM / "SECURITY SUBSYSTEM" entry up to date with the
> > following changes:
> >
> > * Remove the "(suggested Cc:)" note on the mailing list.  I don't
> > really care if the LSM list is on the To: or Cc: line, I just want
> > folks to include it when appropriate.
> >
> > * Remove the website link.  The website isn't really maintained in
> > any meaningful way so we're going to go ahead and remove it so we
> > lessen the chance of conflicting or confusing information in the
> > future.
> >
> > * Add our patchwork link.  I'm not sure this is of much use for
> > anyone but the maintainer, but there is a provision for including it
> > here so we might as well include it.
> >
> > * Add a bug report URI.  I suspect most everyone knows to send mail
> > to the mailing list if they hit a bug, but let's make it official.
> >
> > * Add a link to the LSM tree process/management documentation.  While
> > the doc exists both in the canonical kernel.org location and the
> > GitHub mirror, provide a link to the mirror as GitHub does a better
> > job rendering the Markdown.
> >
> > * Aside from changes to the LSM code itself, we also would like to be
> > notified when the LSMM call sites are changed so we are adding a
> > security_XXX(...) regex to try and catch all of the callers.
> >
> > Signed-off-by: Paul Moore <paul@paul-moore.com>
> > ---
> >  MAINTAINERS | 7 +++++--
> >  1 file changed, 5 insertions(+), 2 deletions(-)
> >
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index 2482b40fd786..007e43ee3e47 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -19507,14 +19507,17 @@ SECURITY SUBSYSTEM
> >  M:     Paul Moore <paul@paul-moore.com>
> >  M:     James Morris <jmorris@namei.org>
> >  M:     "Serge E. Hallyn" <serge@hallyn.com>
> > -L:     linux-security-module@vger.kernel.org (suggested Cc:)
> > +L:     linux-security-module@vger.kernel.org
> >  S:     Supported
> > -W:     http://kernsec.org/
> > +Q:     https://patchwork.kernel.org/project/linux-security-module/list
> > +B:     mailto:linux-security-module@vger.kernel.org
> > +P:     https://github.com/LinuxSecurityModule/kernel/blob/main/README.md
> >  T:     git git://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/lsm.git
>
> Unfortunately I didn't realize this until the patch hit my inbox, but
> I should also update the tree location to use https instead of git.
> I'll fix that when I merge the patch.

Merged into lsm/dev.

-- 
paul-moore.com

      reply	other threads:[~2023-11-16  4:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-15 16:48 [PATCH] MAINTAINERS: update the LSM entry Paul Moore
2023-11-15 17:21 ` Paul Moore
2023-11-16  4:36   ` Paul Moore [this message]

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=CAHC9VhSjAvDPiUtisP8mNbdPwvi6-8uJUbgoRv0GzYZ5-c_qtg@mail.gmail.com \
    --to=paul@paul-moore.com \
    --cc=linux-security-module@vger.kernel.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).