All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tushar Sugandhi <tusharsu@linux.microsoft.com>
To: Mimi Zohar <zohar@linux.ibm.com>,
	stephen.smalley.work@gmail.com, casey@schaufler-ca.com,
	agk@redhat.com, snitzer@redhat.com, gmazyland@gmail.com,
	paul@paul-moore.com
Cc: sashal@kernel.org, dm-devel@redhat.com, selinux@vger.kernel.org,
	jmorris@namei.org, linux-kernel@vger.kernel.org,
	nramas@linux.microsoft.com,
	linux-security-module@vger.kernel.org,
	tyhicks@linux.microsoft.com, linux-integrity@vger.kernel.org
Subject: Re: [dm-devel] [PATCH v10 5/8] IMA: limit critical data measurement based on a label
Date: Thu, 14 Jan 2021 09:57:27 -0800	[thread overview]
Message-ID: <3105b0b9-4e74-691c-56ab-6ca183cb2038@linux.microsoft.com> (raw)
In-Reply-To: <73a82dff7be151298f51c0db6f3c4996ccf44a19.camel@linux.ibm.com>



On 2021-01-13 6:09 p.m., Mimi Zohar wrote:
> On Thu, 2021-01-07 at 20:07 -0800, Tushar Sugandhi wrote:
>> Integrity critical data may belong to a single subsystem or it may
>> arise from cross subsystem interaction.  Currently there is no mechanism
>> to group or limit the data based on certain label.  Limiting and
>> grouping critical data based on a label would make it flexible and
>> configurable to measure.
>>
>> Define "label:=", a new IMA policy condition, for the IMA func
>> CRITICAL_DATA to allow grouping and limiting measurement of integrity
>> critical data.
>>
>> Limit the measurement to the labels that are specified in the IMA
>> policy - CRITICAL_DATA+"label:=".  If "label:=" is not provided with
>> the func CRITICAL_DATA, measure all the input integrity critical data.
>>
>> Signed-off-by: Tushar Sugandhi <tusharsu@linux.microsoft.com>
>> Reviewed-by: Tyler Hicks <tyhicks@linux.microsoft.com>
> 
> This is looking a lot better.
> 
> thanks,
> 
> Mimi
> 
Thanks a lot for the feedback Mimi.
Appreciate it. :)

~Tushar

--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel


WARNING: multiple messages have this Message-ID (diff)
From: Tushar Sugandhi <tusharsu@linux.microsoft.com>
To: Mimi Zohar <zohar@linux.ibm.com>,
	stephen.smalley.work@gmail.com, casey@schaufler-ca.com,
	agk@redhat.com, snitzer@redhat.com, gmazyland@gmail.com,
	paul@paul-moore.com
Cc: tyhicks@linux.microsoft.com, sashal@kernel.org,
	jmorris@namei.org, nramas@linux.microsoft.com,
	linux-integrity@vger.kernel.org, selinux@vger.kernel.org,
	linux-security-module@vger.kernel.org,
	linux-kernel@vger.kernel.org, dm-devel@redhat.com
Subject: Re: [PATCH v10 5/8] IMA: limit critical data measurement based on a label
Date: Thu, 14 Jan 2021 09:57:27 -0800	[thread overview]
Message-ID: <3105b0b9-4e74-691c-56ab-6ca183cb2038@linux.microsoft.com> (raw)
In-Reply-To: <73a82dff7be151298f51c0db6f3c4996ccf44a19.camel@linux.ibm.com>



On 2021-01-13 6:09 p.m., Mimi Zohar wrote:
> On Thu, 2021-01-07 at 20:07 -0800, Tushar Sugandhi wrote:
>> Integrity critical data may belong to a single subsystem or it may
>> arise from cross subsystem interaction.  Currently there is no mechanism
>> to group or limit the data based on certain label.  Limiting and
>> grouping critical data based on a label would make it flexible and
>> configurable to measure.
>>
>> Define "label:=", a new IMA policy condition, for the IMA func
>> CRITICAL_DATA to allow grouping and limiting measurement of integrity
>> critical data.
>>
>> Limit the measurement to the labels that are specified in the IMA
>> policy - CRITICAL_DATA+"label:=".  If "label:=" is not provided with
>> the func CRITICAL_DATA, measure all the input integrity critical data.
>>
>> Signed-off-by: Tushar Sugandhi <tusharsu@linux.microsoft.com>
>> Reviewed-by: Tyler Hicks <tyhicks@linux.microsoft.com>
> 
> This is looking a lot better.
> 
> thanks,
> 
> Mimi
> 
Thanks a lot for the feedback Mimi.
Appreciate it. :)

~Tushar

  reply	other threads:[~2021-01-14 17:57 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-08  4:07 [dm-devel] [PATCH v10 0/8] IMA: support for measuring kernel integrity critical data Tushar Sugandhi
2021-01-08  4:07 ` Tushar Sugandhi
2021-01-08  4:07 ` [dm-devel] [PATCH v10 1/8] IMA: generalize keyring specific measurement constructs Tushar Sugandhi
2021-01-08  4:07   ` Tushar Sugandhi
2021-01-08  4:07 ` [dm-devel] [PATCH v10 2/8] IMA: add support to measure buffer data hash Tushar Sugandhi
2021-01-08  4:07   ` Tushar Sugandhi
2021-01-08  4:07 ` [dm-devel] [PATCH v10 3/8] IMA: define a hook to measure kernel integrity critical data Tushar Sugandhi
2021-01-08  4:07   ` Tushar Sugandhi
2021-01-08  4:07 ` [dm-devel] [PATCH v10 4/8] IMA: add policy rule to measure " Tushar Sugandhi
2021-01-08  4:07   ` Tushar Sugandhi
2021-01-08  4:07 ` [dm-devel] [PATCH v10 5/8] IMA: limit critical data measurement based on a label Tushar Sugandhi
2021-01-08  4:07   ` Tushar Sugandhi
2021-01-14  2:09   ` [dm-devel] " Mimi Zohar
2021-01-14  2:09     ` Mimi Zohar
2021-01-14 17:57     ` Tushar Sugandhi [this message]
2021-01-14 17:57       ` Tushar Sugandhi
2021-01-08  4:07 ` [dm-devel] [PATCH v10 6/8] IMA: extend critical data hook to limit the " Tushar Sugandhi
2021-01-08  4:07   ` Tushar Sugandhi
2021-01-08  4:07 ` [dm-devel] [PATCH v10 7/8] IMA: define a builtin critical data measurement policy Tushar Sugandhi
2021-01-08  4:07   ` Tushar Sugandhi
2021-01-08  4:07 ` [dm-devel] [PATCH v10 8/8] selinux: include a consumer of the new IMA critical data hook Tushar Sugandhi
2021-01-08  4:07   ` Tushar Sugandhi
2021-01-12 16:27   ` [dm-devel] " Paul Moore
2021-01-12 16:27     ` Paul Moore
2021-01-12 18:25     ` [dm-devel] " Lakshmi Ramasubramanian
2021-01-12 18:25       ` Lakshmi Ramasubramanian
2021-01-13 19:13     ` [dm-devel] " Mimi Zohar
2021-01-13 19:13       ` Mimi Zohar
2021-01-13 19:19       ` [dm-devel] " Paul Moore
2021-01-13 19:19         ` Paul Moore
2021-01-13 21:11         ` [dm-devel] " Mimi Zohar
2021-01-13 21:11           ` Mimi Zohar
2021-01-13 22:10           ` [dm-devel] " Paul Moore
2021-01-13 22:10             ` Paul Moore
2021-01-13 23:10             ` [dm-devel] " Mimi Zohar
2021-01-13 23:10               ` Mimi Zohar
2021-01-14  2:40               ` [dm-devel] " Paul Moore
2021-01-14  2:40                 ` Paul Moore
2021-01-14  2:49                 ` [dm-devel] " Mimi Zohar
2021-01-14  2:49                   ` Mimi Zohar
2021-01-14 16:22                   ` [dm-devel] " Lakshmi Ramasubramanian
2021-01-14 16:22                     ` Lakshmi Ramasubramanian
2021-01-14 16:44                     ` [dm-devel] " Mimi Zohar
2021-01-14 16:44                       ` Mimi Zohar
2021-01-14 16:50                       ` [dm-devel] " Mimi Zohar
2021-01-14 16:50                         ` Mimi Zohar
2021-01-14 17:48                         ` [dm-devel] " Lakshmi Ramasubramanian
2021-01-14 17:48                           ` Lakshmi Ramasubramanian
2021-01-14 19:21                           ` [dm-devel] " Lakshmi Ramasubramanian
2021-01-14 19:21                             ` Lakshmi Ramasubramanian
2021-01-14 16:51                       ` [dm-devel] " Paul Moore
2021-01-14 16:51                         ` Paul Moore
2021-01-15 12:54 ` [dm-devel] [PATCH v10 0/8] IMA: support for measuring kernel integrity critical data Mimi Zohar
2021-01-15 12:54   ` Mimi Zohar
2021-01-15 17:26   ` [dm-devel] " Tushar Sugandhi
2021-01-15 17:26     ` Tushar Sugandhi

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=3105b0b9-4e74-691c-56ab-6ca183cb2038@linux.microsoft.com \
    --to=tusharsu@linux.microsoft.com \
    --cc=agk@redhat.com \
    --cc=casey@schaufler-ca.com \
    --cc=dm-devel@redhat.com \
    --cc=gmazyland@gmail.com \
    --cc=jmorris@namei.org \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=nramas@linux.microsoft.com \
    --cc=paul@paul-moore.com \
    --cc=sashal@kernel.org \
    --cc=selinux@vger.kernel.org \
    --cc=snitzer@redhat.com \
    --cc=stephen.smalley.work@gmail.com \
    --cc=tyhicks@linux.microsoft.com \
    --cc=zohar@linux.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.