All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@google.com>
To: Mikhail Kurinnoi <viewizard@viewizard.com>
Cc: Paul Moore <paul@paul-moore.com>,
	Stephen Smalley <sds@tycho.nsa.gov>,
	Eric Paris <eparis@parisplace.org>,
	selinux@tycho.nsa.gov, Casey Schaufler <casey@schaufler-ca.com>,
	linux-security-module@vger.kernel.org,
	Mimi Zohar <zohar@linux.vnet.ibm.com>,
	Dmitry Kasatkin <dmitry.kasatkin@gmail.com>,
	linux-integrity <linux-integrity@vger.kernel.org>
Subject: Re: [PATCH 2/2] IMA: Support using new creds in appraisal policy
Date: Mon, 16 Oct 2017 14:20:11 -0700	[thread overview]
Message-ID: <CACdnJusGBTLVDtc4h3ycgZsFBhA8Ly2HZ559iPTOAOP9vZrnyg@mail.gmail.com> (raw)
In-Reply-To: <20171017000303.46e56b42@totoro>

On Mon, Oct 16, 2017 at 2:03 PM, Mikhail Kurinnoi
<viewizard@viewizard.com> wrote:
> В Mon, 16 Oct 2017 13:37:09 -0700
> Matthew Garrett <mjg59@google.com> пишет:
>>  #define IMA_BPRM_APPRAISED   0x00002000
>>  #define IMA_READ_APPRAISE    0x00004000
>>  #define IMA_READ_APPRAISED   0x00008000
>> +#define IMA_CREDS_APPRAISE   0x00004000
>> +#define IMA_CREDS_APPRAISED  0x00008000
>
> Is this correct, that the IMA_CREDS_APPRAISE and IMA_CREDS_APPRAISED
> same as IMA_READ_APPRAISE and IMA_READ_APPRAISED?

Definitely not correct, good catch. I'll resend with that fixed if
people feel this approach is reasonable.

WARNING: multiple messages have this Message-ID (diff)
From: mjg59@google.com (Matthew Garrett)
To: linux-security-module@vger.kernel.org
Subject: [PATCH 2/2] IMA: Support using new creds in appraisal policy
Date: Mon, 16 Oct 2017 14:20:11 -0700	[thread overview]
Message-ID: <CACdnJusGBTLVDtc4h3ycgZsFBhA8Ly2HZ559iPTOAOP9vZrnyg@mail.gmail.com> (raw)
In-Reply-To: <20171017000303.46e56b42@totoro>

On Mon, Oct 16, 2017 at 2:03 PM, Mikhail Kurinnoi
<viewizard@viewizard.com> wrote:
> ? Mon, 16 Oct 2017 13:37:09 -0700
> Matthew Garrett <mjg59@google.com> ?????:
>>  #define IMA_BPRM_APPRAISED   0x00002000
>>  #define IMA_READ_APPRAISE    0x00004000
>>  #define IMA_READ_APPRAISED   0x00008000
>> +#define IMA_CREDS_APPRAISE   0x00004000
>> +#define IMA_CREDS_APPRAISED  0x00008000
>
> Is this correct, that the IMA_CREDS_APPRAISE and IMA_CREDS_APPRAISED
> same as IMA_READ_APPRAISE and IMA_READ_APPRAISED?

Definitely not correct, good catch. I'll resend with that fixed if
people feel this approach is reasonable.
--
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

WARNING: multiple messages have this Message-ID (diff)
From: Matthew Garrett <mjg59@google.com>
To: Mikhail Kurinnoi <viewizard@viewizard.com>
Cc: Paul Moore <paul@paul-moore.com>,
	Stephen Smalley <sds@tycho.nsa.gov>,
	Eric Paris <eparis@parisplace.org>,
	selinux@tycho.nsa.gov, Casey Schaufler <casey@schaufler-ca.com>,
	linux-security-module@vger.kernel.org,
	Mimi Zohar <zohar@linux.vnet.ibm.com>,
	Dmitry Kasatkin <dmitry.kasatkin@gmail.com>,
	linux-integrity <linux-integrity@vger.kernel.org>
Subject: Re: [PATCH 2/2] IMA: Support using new creds in appraisal policy
Date: Mon, 16 Oct 2017 14:20:11 -0700	[thread overview]
Message-ID: <CACdnJusGBTLVDtc4h3ycgZsFBhA8Ly2HZ559iPTOAOP9vZrnyg@mail.gmail.com> (raw)
In-Reply-To: <20171017000303.46e56b42@totoro>

On Mon, Oct 16, 2017 at 2:03 PM, Mikhail Kurinnoi
<viewizard@viewizard.com> wrote:
> ? Mon, 16 Oct 2017 13:37:09 -0700
> Matthew Garrett <mjg59@google.com> ?????:
>>  #define IMA_BPRM_APPRAISED   0x00002000
>>  #define IMA_READ_APPRAISE    0x00004000
>>  #define IMA_READ_APPRAISED   0x00008000
>> +#define IMA_CREDS_APPRAISE   0x00004000
>> +#define IMA_CREDS_APPRAISED  0x00008000
>
> Is this correct, that the IMA_CREDS_APPRAISE and IMA_CREDS_APPRAISED
> same as IMA_READ_APPRAISE and IMA_READ_APPRAISED?

Definitely not correct, good catch. I'll resend with that fixed if
people feel this approach is reasonable.

  reply	other threads:[~2017-10-16 21:20 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-16 20:37 [PATCH 1/2] security: Add a cred_getsecid hook Matthew Garrett
2017-10-16 20:37 ` Matthew Garrett
2017-10-16 20:37 ` [PATCH 2/2] IMA: Support using new creds in appraisal policy Matthew Garrett
2017-10-16 20:37   ` Matthew Garrett
2017-10-16 21:03   ` Mikhail Kurinnoi
2017-10-16 21:03     ` Mikhail Kurinnoi
2017-10-16 21:03     ` Mikhail Kurinnoi
2017-10-16 21:20     ` Matthew Garrett [this message]
2017-10-16 21:20       ` Matthew Garrett
2017-10-16 21:20       ` Matthew Garrett
2017-10-17 19:07   ` Mimi Zohar
2017-10-17 19:07     ` Mimi Zohar
2017-10-17 19:07     ` Mimi Zohar
2017-10-18 20:59     ` Matthew Garrett
2017-10-18 20:59       ` Matthew Garrett
2017-10-16 21:58 ` [PATCH 1/2] security: Add a cred_getsecid hook Casey Schaufler
2017-10-16 21:58   ` Casey Schaufler
2017-10-18 21:01   ` Matthew Garrett
2017-10-18 21:01     ` Matthew Garrett
2017-10-23 23:20 ` Paul Moore
2017-10-23 23:20   ` Paul Moore
2017-10-19 23:14 Matthew Garrett
2017-10-19 23:14 ` [PATCH 2/2] IMA: Support using new creds in appraisal policy Matthew Garrett
2017-10-19 23:14   ` 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=CACdnJusGBTLVDtc4h3ycgZsFBhA8Ly2HZ559iPTOAOP9vZrnyg@mail.gmail.com \
    --to=mjg59@google.com \
    --cc=casey@schaufler-ca.com \
    --cc=dmitry.kasatkin@gmail.com \
    --cc=eparis@parisplace.org \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=paul@paul-moore.com \
    --cc=sds@tycho.nsa.gov \
    --cc=selinux@tycho.nsa.gov \
    --cc=viewizard@viewizard.com \
    --cc=zohar@linux.vnet.ibm.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 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.