linux-security-module.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Serge E. Hallyn" <serge@hallyn.com>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Cc: Paul Moore <paul@paul-moore.com>, linux-security-module@vger.kernel.org
Subject: Re: ANN: new LSM guidelines
Date: Mon, 11 Sep 2023 08:03:47 -0500	[thread overview]
Message-ID: <20230911130347.GA1613433@mail.hallyn.com> (raw)
In-Reply-To: <f8f32da5-6f31-d197-7405-8f308bd29228@I-love.SAKURA.ne.jp>

On Sat, Sep 09, 2023 at 09:46:02AM +0900, Tetsuo Handa wrote:
> On 2023/08/03 7:00, Paul Moore wrote:
> > * The new LSM must be sufficiently unique to justify the additional work
> > involved in reviewing, maintaining, and supporting the LSM.  It is reasonable
> > for there to be a level of overlap between LSMs, but either the security model
> > or the admin/user experience must be significantly unique.
> 
> s/work/burden/ ?
> 
> > * Any userspace tools or patches created in support of the LSM must be publicly
> > available, with a public git repository preferable over a tarball snapshot.
> 
> What is the definition of "publicly" here? Everyone can download related resources
> including the source code etc. anonymously (e.g. without asking for creating user
> account and/or buying subscriptions ) ?

Hm, that's a good point actually.  I would say that one must be able to fully
administer it with free (in both senses) tools, which must be used (let's aim
for the moon) in an included testsuite.  However, that doesn't need to be true
of "any" support tools.  If the author wants to sell some improved tools,  I
think that's good.  But again, the free tools must always be able to configure
every aspect of the LSM.

-serge

  reply	other threads:[~2023-09-11 22:09 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-06 20:42 ANN: new LSM guidelines Paul Moore
2023-07-07  0:32 ` Casey Schaufler
2023-07-07 22:02   ` Paul Moore
2023-08-01 22:47     ` Paul Moore
2023-08-02 18:38       ` Mickaël Salaün
2023-08-02 21:56         ` Paul Moore
2023-08-02 22:36           ` Randy Dunlap
2023-08-03 20:55             ` Paul Moore
2023-08-03  9:44           ` Mickaël Salaün
2023-08-03 21:36             ` Paul Moore
2023-08-02 22:00       ` Paul Moore
2023-08-03  9:44         ` Mickaël Salaün
2023-08-03 21:24           ` Paul Moore
2023-08-03 21:38         ` Paul Moore
2023-08-04  7:58           ` Mickaël Salaün
2023-08-07 21:52             ` Paul Moore
2023-09-07 22:12           ` Paul Moore
2023-09-08 16:02             ` Casey Schaufler
2023-09-08 17:29               ` Paul Moore
2023-09-08 20:53                 ` Casey Schaufler
2023-09-09  0:46         ` Tetsuo Handa
2023-09-11 13:03           ` Serge E. Hallyn [this message]
2023-09-11 20:04           ` Paul Moore
2023-09-12  1:29             ` Tetsuo Handa
2023-09-12 18:08               ` Paul Moore
2023-09-12 18:39                 ` Casey Schaufler
2023-09-12 19:00                   ` Paul Moore
2023-09-12 19:03                     ` Paul Moore
2023-09-25  0:55                     ` Tetsuo Handa
2023-09-25  1:32                       ` Kees Cook
2023-09-25  4:32                         ` Tetsuo Handa
2023-09-26 21:23                           ` Paul Moore
2023-09-15 11:29                 ` Tetsuo Handa

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=20230911130347.GA1613433@mail.hallyn.com \
    --to=serge@hallyn.com \
    --cc=linux-security-module@vger.kernel.org \
    --cc=paul@paul-moore.com \
    --cc=penguin-kernel@I-love.SAKURA.ne.jp \
    /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).