From: Casey Schaufler <casey@schaufler-ca.com>
To: Steve Kemp <steve.backup.kemp@googlemail.com>
Cc: linux-security-module <linux-security-module@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [RFC 0/3] WhiteEgret LSM module
Date: Fri, 2 Jun 2017 12:00:22 -0700 [thread overview]
Message-ID: <e26e9aa2-12b2-4aac-092b-747e8be160a3@schaufler-ca.com> (raw)
In-Reply-To: <CABxV-EX8C175BRvYdKO8BObCQ5V30=ge8rE7SeSOzTrADgxxDg@mail.gmail.com>
On 6/2/2017 10:39 AM, Steve Kemp wrote:
>> Create an security module that looks for the attribute
> For what it is worth I thought this seemed like an interesting project
> for a beginner, so I did just that. I wrote up the experience here:
>
> https://blog.steve.fi/so_i_accidentally_wrote_a_linux_security_module.html
>
> In short it was a very simple and clean approach, which I think is
> hard to get wrong. The only part I need to work on some more is the
> difference between `user` and `security` attributes.
A 'user' attribute can be set by the file owner. A 'security'
attribute requires privilege. SELinux and Smack use 'security'
attributes to prevent users from mucking with them. You need
to create module hooks for manipulating them, including
inode_init_security
inode_setxattr
inode_post_setxattr
inode_removexattr
inode_getsecurity
inode_listsecurity
inode_setsecurity
d_instantiate
>
> Steve
> --
> https://steve.fi/
>
next prev parent reply other threads:[~2017-06-02 19:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-30 11:11 Masanobu Koike
2017-05-30 17:18 ` Casey Schaufler
2017-06-06 9:28 ` masanobu2.koike
2017-05-30 20:50 ` Matthew Garrett
2017-05-31 10:59 ` Peter Dolding
2017-05-31 15:22 ` Casey Schaufler
2017-05-31 15:35 ` Serge E. Hallyn
2017-06-04 2:43 ` Peter Dolding
2017-06-04 16:25 ` Serge E. Hallyn
2017-06-02 17:39 ` Steve Kemp
2017-06-02 19:00 ` Casey Schaufler [this message]
2017-06-02 20:28 ` Steve Kemp
2017-05-31 15:36 ` Mehmet Kayaalp
2017-06-04 2:21 ` Peter Dolding
2017-06-04 18:51 ` Mehmet Kayaalp
2017-06-15 7:56 ` masanobu2.koike
2017-06-01 12:31 ` masanobu2.koike
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=e26e9aa2-12b2-4aac-092b-747e8be160a3@schaufler-ca.com \
--to=casey@schaufler-ca.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=steve.backup.kemp@googlemail.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
all inboxes | Powered by JetHome®