From: Joshua Brindle <jbrindle@snu.edu>
To: Stephen Smalley <sds@epoch.ncsc.mil>
Cc: Valdis.Kletnieks@vt.edu, selinux@tycho.nsa.gov
Subject: Re: Linux 2.6.6-rc3-mm2 and SELinux support of stacked modules
Date: Thu, 13 May 2004 15:36:29 -0500 [thread overview]
Message-ID: <40A3DC4D.1030401@snu.edu> (raw)
In-Reply-To: <1084470920.14586.119.camel@moss-spartans.epoch.ncsc.mil>
Stephen Smalley wrote:
>On Sun, 2004-05-09 at 22:38, Valdis.Kletnieks@vt.edu wrote:
>
>
>>I've attached a patch that does the secondary_ops callback for essentially
>>everything used by either my already-written code, in-progress code, or the
>>BSDJail module.
>>
>>
>
>A couple of notes regarding your insertion of secondary_ops calls:
>
>1) Joshua Brindle (cc'd) posted a patch to this list earlier to likewise
>add secondary ops for another security module. There were two points of
>overlap: inode_permission and file_mmap. In the case of
>inode_permission, you both inserted the secondary hook call after the
>null mask test (existence test). Are you sure that you will never want
>to see such calls in a secondary module? In the case of file_mmap,
>Joshua's diff only calls the secondary module if there is a file struct,
>whereas your diff always calls the secondary module. The latter offers
>greater flexibility to the secondary module, so I'm inclined to use it,
>but thought I should note it as it means that the secondary module will
>need to test for the null file case and act accordingly.
>
>2) Neither the post_mountroot nor pivotroot hooks are likely to survive
>long term IMHO, so I don't plan on adding them to the SELinux module.
>
>
>
It might be a better idea for other modules to call the secondary module
before the check, I wasn't too concerned about it for the module I was
working on but it might be an issue for others.
Joshua Brindle
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2004-05-13 20:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-10 2:38 Linux 2.6.6-rc3-mm2 and SELinux support of stacked modules Valdis.Kletnieks
2004-05-10 18:32 ` Serge Hallyn
2004-05-10 19:21 ` Valdis.Kletnieks
2004-05-10 18:38 ` Stephen Smalley
2004-05-10 19:24 ` Valdis.Kletnieks
2004-05-13 17:55 ` Stephen Smalley
2004-05-13 20:36 ` Joshua Brindle [this message]
2004-05-13 21:54 ` Valdis.Kletnieks
2004-05-17 12:34 ` Stephen Smalley
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=40A3DC4D.1030401@snu.edu \
--to=jbrindle@snu.edu \
--cc=Valdis.Kletnieks@vt.edu \
--cc=sds@epoch.ncsc.mil \
--cc=selinux@tycho.nsa.gov \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.