From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
To: tixxdz@gmail.com
Cc: linux-kernel@vger.kernel.org,
kernel-hardening@lists.openwall.com,
linux-security-module@vger.kernel.org, keescook@chromium.org,
akpm@linux-foundation.org, wluikil@gmail.com,
dongsu@endocode.com, luto@kernel.org, james.l.morris@oracle.com,
serge@hallyn.com, viro@zeniv.linux.org.uk, daniel@zonque.org,
jann@thejh.net, elena.reshetova@intel.com
Subject: Re: [RFC/PATCH 1/3] security: add the security_task_copy() hook
Date: Mon, 6 Feb 2017 19:49:49 +0900 [thread overview]
Message-ID: <201702061949.HGE43791.FFFtJVSHQOOLOM@I-love.SAKURA.ne.jp> (raw)
In-Reply-To: <1486055094-4532-2-git-send-email-djalal@gmail.com>
Djalal Harouni wrote:
> To achieve the above we add the security_task_copy() hook that allows us
> to clone the Timgad context of parent into child task_struct.
>
> The security hook can also be used by new LSMs after the child task has
> done some initialization, this way they won't clash with the major LSMs.
> The situation is not really well, this hook allows us to introduce a
> stackable LSM that can be easily used with all other LSMs.
We are already planning to revive security_task_alloc() hook (probably in Linux 4.12)
( news://news.gmane.org:119/201701101958.JAD43709.OtJSOQFVFOLHMF@I-love.SAKURA.ne.jp ).
Is security_task_alloc() called too early for your case?
(Well, we want to configure http archive like marc.info ?)
next prev parent reply other threads:[~2017-02-06 10:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-02 17:04 [RFC/PATCH 0/3] introduce Timgad LSM Djalal Harouni
2017-02-02 17:04 ` [RFC/PATCH 1/3] security: add the security_task_copy() hook Djalal Harouni
2017-02-06 10:49 ` Tetsuo Handa [this message]
2017-02-06 12:40 ` Djalal Harouni
2017-02-06 13:10 ` Djalal Harouni
2017-02-02 17:04 ` [RFC/PATCH 2/3] security: Add the Timgad module Djalal Harouni
2017-02-03 1:02 ` James Morris
2017-02-06 12:19 ` Djalal Harouni
2017-02-11 0:33 ` Kees Cook
2017-02-14 12:19 ` Djalal Harouni
2017-02-02 17:04 ` [RFC/PATCH 3/3] doc: add Timgad LSM documentation Djalal Harouni
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=201702061949.HGE43791.FFFtJVSHQOOLOM@I-love.SAKURA.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=akpm@linux-foundation.org \
--cc=daniel@zonque.org \
--cc=dongsu@endocode.com \
--cc=elena.reshetova@intel.com \
--cc=james.l.morris@oracle.com \
--cc=jann@thejh.net \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=luto@kernel.org \
--cc=serge@hallyn.com \
--cc=tixxdz@gmail.com \
--cc=viro@zeniv.linux.org.uk \
--cc=wluikil@gmail.com \
/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).