From: James Morris <jmorris@namei.org>
To: Casey Schaufler <casey@schaufler-ca.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Paul Moore <paul@paul-moore.com>,
selinux@vger.kernel.org,
LSM List <linux-security-module@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] SELinux patches for v5.8
Date: Thu, 4 Jun 2020 12:13:09 +1000 (AEST) [thread overview]
Message-ID: <alpine.LRH.2.21.2006041212110.335@namei.org> (raw)
In-Reply-To: <761f5d15-3422-1834-7be5-8f3276d10172@schaufler-ca.com>
On Wed, 3 Jun 2020, Casey Schaufler wrote:
> On 6/3/2020 3:12 PM, James Morris wrote:
> > On Wed, 3 Jun 2020, Casey Schaufler wrote:
> >
> >> The use of security modules was expected to be rare.
> > This is not correct. Capabilities were ported to LSM and stacked from the
> > beginning, and several major distros worked on LSM so they could ship
> > their own security modules.
>
> Capabilities has always been a special case.
> Until Android adopted SELinux the actual use of LSMs was rare.
Nope, it was enabled by default in several distros and very widely
deployed in the govt space (at least).
--
James Morris
<jmorris@namei.org>
next prev parent reply other threads:[~2020-06-04 2:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-02 1:06 [GIT PULL] SELinux patches for v5.8 Paul Moore
2020-06-03 0:31 ` Linus Torvalds
2020-06-03 17:20 ` Casey Schaufler
2020-06-03 17:37 ` Linus Torvalds
2020-06-03 18:05 ` Casey Schaufler
2020-06-03 21:02 ` Alexei Starovoitov
2020-06-03 22:00 ` Casey Schaufler
2020-06-03 23:38 ` Alexei Starovoitov
2020-06-03 22:12 ` James Morris
2020-06-03 22:38 ` Casey Schaufler
2020-06-04 2:13 ` James Morris [this message]
2020-06-04 12:45 ` Stephen Smalley
2020-06-04 15:28 ` Casey Schaufler
2020-06-04 15:33 ` Stephen Smalley
2020-06-03 23:35 ` Paul Moore
2020-06-03 1:10 ` pr-tracker-bot
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=alpine.LRH.2.21.2006041212110.335@namei.org \
--to=jmorris@namei.org \
--cc=casey@schaufler-ca.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=selinux@vger.kernel.org \
--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).