From: sargun@sargun.me (Sargun Dhillon)
To: linux-security-module@vger.kernel.org
Subject: [RFC 0/3] Safe, dynamically (un)loadable LSMs
Date: Thu, 7 Dec 2017 16:14:58 -0800 [thread overview]
Message-ID: <CAMp4zn_1C+ko41sB4pmr7qWi8Y3eeWFnqU0WqpmeuPN3Qjpp7Q@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.20.1712071053420.8348@localhost>
On Wed, Dec 6, 2017 at 4:00 PM, James Morris <james.l.morris@oracle.com> wrote:
> On Wed, 6 Dec 2017, Sargun Dhillon wrote:
>
>> Should I respin this patch sans module unloading? Still a set of dynamic
>> hooks that are independent to allow for sealable memory support.
>
> Yes, please.
>
>> I'm also wondering what people think of the fs change? I don't think
>> that it makes a lot of sense just having one giant list. I was thinking
>> it might make more sense using the module_name instead.
>
> I don't know how useful this will be in practice. Who/what will be
> looking at these entries and why?
For the same reason you look at iptables -L -n -- to figure out what's
being invoked,
and what's causing rejections (or falsely accepting requests). In addition,
this is for minor LSMs, so the traditional /sys/kernel/security/lsm doesn't make
a lot of sense in my opinion, as it's not broken out per-hook. Given
that this can
be registered per-hook, versus globally, I think that breaking out the LSMs per
hook makes more sense.
It also can be used to determine if a hook was loaded after boot, if the global
invocations is greater than the invocations of the instance of that hook.
>
>
> --
> James Morris
> <james.l.morris@oracle.com>
>
--
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
prev parent reply other threads:[~2017-12-08 0:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-26 22:15 [RFC 0/3] Safe, dynamically (un)loadable LSMs Sargun Dhillon
2017-11-30 2:28 ` Casey Schaufler
2017-12-01 11:17 ` Igor Stoppa
2017-12-05 10:02 ` Sargun Dhillon
2017-12-05 22:56 ` Casey Schaufler
2017-12-06 17:07 ` Sargun Dhillon
2017-12-07 0:00 ` James Morris
2017-12-08 0:14 ` Sargun Dhillon [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=CAMp4zn_1C+ko41sB4pmr7qWi8Y3eeWFnqU0WqpmeuPN3Qjpp7Q@mail.gmail.com \
--to=sargun@sargun.me \
--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;
as well as URLs for NNTP newsgroup(s).