From: Denis Obrezkov <denisobrezkov@gmail.com>
To: linux-security-module@vger.kernel.org
Subject: SMACK: how are smack blobs getting into cred->security and inode->i_security?
Date: Fri, 31 Dec 2021 14:08:04 +0100 [thread overview]
Message-ID: <470651da-88da-8a9e-7ba1-c5f36066bf72@gmail.com> (raw)
Hello,
I am trying to understand how smack works (looking at
smack_inode_permission hook). I can see that that smack security
information is taken from cred->security and inode->i_security but how
did they get in there? Also, when does it happen? (for a task and for a
file)
--
Regards, Denis Obrezkov
next reply other threads:[~2021-12-31 13:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-31 13:08 Denis Obrezkov [this message]
2021-12-31 17:25 ` SMACK: how are smack blobs getting into cred->security and inode->i_security? Casey Schaufler
2022-01-01 21:34 ` Denis Obrezkov
2022-01-02 21:26 ` Casey Schaufler
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=470651da-88da-8a9e-7ba1-c5f36066bf72@gmail.com \
--to=denisobrezkov@gmail.com \
--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