From: Paul Moore <paul@paul-moore.com>
To: linux-security-module@vger.kernel.org, linux-audit@redhat.com,
selinux@vger.kernel.org
Cc: Richard Guy Briggs <rgb@redhat.com>,
John Johansen <john.johansen@canonical.com>
Subject: Re: [PATCH v2 0/3] Split security_task_getsecid() into subj and obj variants
Date: Mon, 22 Mar 2021 15:29:31 -0400 [thread overview]
Message-ID: <CAHC9VhRF4xRQiu+iww=G3FkY2vcjFuPAj4=5yVW4dxCYSnF1NA@mail.gmail.com> (raw)
In-Reply-To: <161609713992.55424.6906498317563652734.stgit@olly>
On Thu, Mar 18, 2021 at 4:42 PM Paul Moore <paul@paul-moore.com> wrote:
>
> An update on the previous RFC patchset found here:
>
> https://lore.kernel.org/linux-security-module/161377712068.87807.12246856567527156637.stgit@sifl/
>
> Aside from being rebased to the current SELinux next branch (which
> in turn is based on v5.12-rc2), this revision changes the binder
> related code to always use the objective credentials as discussed
> in the thread above. I've also dropped the AppArmor patch as John
> has a better version in progress; in the meantime AppArmor should
> continue to work exactly as it did before this patchset so there
> is no harm in merging this without the AppArmor patch.
>
> Casey, John, and Richard; I dropped your ACKs, Reviewed-by, etc.
> tags as the binder changes seemed substantial enough to not
> carryover your tags. I would appreciate it if you could re-review
> this revision; the changes should be minimal. I did leave Mimi's
> tag on this revision as she qualified it for IMA and that code
> didn't change.
>
> ---
>
> Paul Moore (3):
> lsm: separate security_task_getsecid() into subjective and objective variants
> selinux: clarify task subjective and objective credentials
> smack: differentiate between subjective and objective task credentials
>
>
> security/selinux/hooks.c | 112 ++++++++++++++++++++++++-------------
> security/smack/smack.h | 18 +++++-
> security/smack/smack_lsm.c | 40 ++++++++-----
> 3 files changed, 117 insertions(+), 53 deletions(-)
All three patches have been merged into selinux/next, thanks for the
help/review everyone!
--
paul moore
www.paul-moore.com
--
Linux-audit mailing list
Linux-audit@redhat.com
https://listman.redhat.com/mailman/listinfo/linux-audit
prev parent reply other threads:[~2021-03-22 19:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-18 20:42 [PATCH v2 0/3] Split security_task_getsecid() into subj and obj variants Paul Moore
2021-03-18 20:42 ` [PATCH v2 1/3] lsm: separate security_task_getsecid() into subjective and objective variants Paul Moore
2021-03-18 20:57 ` Casey Schaufler
2021-03-19 3:44 ` Paul Moore
2021-03-19 13:35 ` Richard Guy Briggs
2021-03-18 20:42 ` [PATCH v2 2/3] selinux: clarify task subjective and objective credentials Paul Moore
2021-03-19 13:36 ` Richard Guy Briggs
2021-03-18 20:42 ` [PATCH v2 3/3] smack: differentiate between subjective and objective task credentials Paul Moore
2021-03-22 19:29 ` 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='CAHC9VhRF4xRQiu+iww=G3FkY2vcjFuPAj4=5yVW4dxCYSnF1NA@mail.gmail.com' \
--to=paul@paul-moore.com \
--cc=john.johansen@canonical.com \
--cc=linux-audit@redhat.com \
--cc=linux-security-module@vger.kernel.org \
--cc=rgb@redhat.com \
--cc=selinux@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).