From: mjg59@google.com (Matthew Garrett)
To: linux-security-module@vger.kernel.org
Subject: [PATCH V4 2/3] IMA: Use consistent creds
Date: Thu, 4 Jan 2018 11:17:14 -0800 [thread overview]
Message-ID: <CACdnJutPiKUTUpS6d7G0zKjrCS8hR3xy1a+Xsi2Chyj7sAvayg@mail.gmail.com> (raw)
In-Reply-To: <bfb721eb-6066-4440-069f-d0089426b787@schaufler-ca.com>
On Wed, Jan 3, 2018 at 12:08 PM, Casey Schaufler <casey@schaufler-ca.com> wrote:
> On 1/3/2018 11:44 AM, Matthew Garrett wrote:
>> If we want to be able to do something conditional on the LSM context
>> that a process is going to be executed under, *before* commit_creds()
>> is called, is there an existing way to do so? I can rework this so we
>> use the task secid for all running processes and the cred secid for
>> the not-yet-running child process, but I don't know if that's
>> sufficient to avoid problems in future.
>
> It's possible that converting all the existing calls of
> security_task_getsecid() to security_cred_getsecid() is the
> safe approach. No one is using the task blob today, and this
> would disambiguate the situation.
Ok. Should we be looking at creds or real_creds?
--
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
next prev parent reply other threads:[~2018-01-04 19:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-03 1:20 [PATCH V4 1/3] security: Add a cred_getsecid hook Matthew Garrett
2018-01-03 1:20 ` [PATCH V4 2/3] IMA: Use consistent creds Matthew Garrett
2018-01-03 15:54 ` Casey Schaufler
2018-01-03 18:11 ` Matthew Garrett
2018-01-03 19:32 ` Casey Schaufler
2018-01-03 19:44 ` Matthew Garrett
2018-01-03 20:08 ` Casey Schaufler
2018-01-04 19:17 ` Matthew Garrett [this message]
2018-01-03 1:20 ` [PATCH V4 3/3] IMA: Support using new creds in appraisal policy Matthew Garrett
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=CACdnJutPiKUTUpS6d7G0zKjrCS8hR3xy1a+Xsi2Chyj7sAvayg@mail.gmail.com \
--to=mjg59@google.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;
as well as URLs for NNTP newsgroup(s).