From: jmorris@namei.org (James Morris)
To: linux-security-module@vger.kernel.org
Subject: [PATCH] TOMOYO: Switch from per "struct cred" blob to per "struct task_struct" blob.
Date: Mon, 13 Mar 2017 10:17:06 +1100 (AEDT) [thread overview]
Message-ID: <alpine.LRH.2.20.1703131012360.2317@namei.org> (raw)
In-Reply-To: <CAEiveUfGHiz_oXgG9cscOF3ErdH9DJtp5zRxyCW+QbpzpYqc1w@mail.gmail.com>
On Sun, 12 Mar 2017, Djalal Harouni wrote:
> ...
Please trim quotes when replying.
> Is it possible to adapt some stacking bits from Casey's patches and
> stack this security field ? or at least try first to stack
> task->security without having to stack all the others cred->security,
> inode->security ... ?
>
> IMO it would be better if the first LSM user gets this right, or at
> least the second LSM that uses the field without having to wait for
> the support of all security fields stacking.
As Tetsuo mentions in the changelog, he aims to revive the hook before
modifying it for stacking. I would also want to see a strong use-case for
the stacking aspect (e.g. an existing LSM planning to use it, or as part
of a proposal to merge a new LSM).
JJ: can you confirm that you'll use the revived hook in AppArmor? I can
see your acked-by but the context of it is lost due to the lack of mail
archives.
--
James Morris
<jmorris@namei.org>
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-03-12 23:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-12 4:41 [PATCH] TOMOYO: Switch from per "struct cred" blob to per "struct task_struct" blob Tetsuo Handa
2017-03-12 21:12 ` Djalal Harouni
2017-03-12 23:17 ` James Morris [this message]
2017-03-12 23:56 ` John Johansen
2017-03-13 5:59 ` James Morris
-- strict thread matches above, loose matches on Subject: below --
2017-03-28 11:02 Tetsuo Handa
2017-03-28 15:26 ` Casey Schaufler
2017-03-30 11:09 ` Tetsuo Handa
2017-03-30 15:06 ` Casey Schaufler
2017-03-31 0:52 ` Tetsuo Handa
2017-03-31 16:09 ` Casey Schaufler
2017-04-01 3:32 ` 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=alpine.LRH.2.20.1703131012360.2317@namei.org \
--to=jmorris@namei.org \
--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