linux-integrity.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Fan Wu <wufan@linux.microsoft.com>
To: Paul Menzel <pmenzel@molgen.mpg.de>, Paul Moore <paul@paul-moore.com>
Cc: corbet@lwn.net, zohar@linux.ibm.com, jmorris@namei.org,
	serge@hallyn.com, tytso@mit.edu, ebiggers@kernel.org,
	axboe@kernel.dk, agk@redhat.com, snitzer@kernel.org,
	mpatocka@redhat.com, eparis@redhat.com,
	linux-doc@vger.kernel.org, linux-integrity@vger.kernel.org,
	linux-security-module@vger.kernel.org, fsverity@lists.linux.dev,
	linux-block@vger.kernel.org, dm-devel@lists.linux.dev,
	audit@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v20 20/20] MAINTAINERS: ipe: add ipe maintainer information
Date: Wed, 7 Aug 2024 11:01:21 -0700	[thread overview]
Message-ID: <080c93d1-9c02-478f-a0be-f4bd3869c1fd@linux.microsoft.com> (raw)
In-Reply-To: <5880e801-e896-4bf0-9a69-2cf5acb51ec3@molgen.mpg.de>



On 8/6/2024 9:48 PM, Paul Menzel wrote:
> Dear Paul,
> 
> 
> Am 06.08.24 um 22:54 schrieb Paul Moore:
>> On Sat, Aug 3, 2024 at 4:15 AM Paul Menzel wrote:
> 
>>> Thank you very much for your patch. Two nits, should you sent another
>>> interation: A more specific summary would avoid people having to look at
>>> the message body or diff, and `git log --oneline` would be enough.
>>>
>>> MAINTAINERS: Add IPE entry with M: Fan Wu
>>>
>>> MAINTAINERS: Add IPE entry with Fan Wu as maintainer
>>>
>>> Am 03.08.24 um 08:08 schrieb Fan Wu:
>>>> Update MAINTAINERS to include ipe maintainer information.
>>>
>>> I’d at least mention Integrity Policy Enforcement. As you not only
>>> include the maintainer information but add a new entry, I’d leave the
>>> body out, or mention that a new entry is added.
>>>
>>>> Signed-off-by: Fan Wu <wufan@linux.microsoft.com>
>>
>> Working under the current assumption that a new revision is not
>> needed, I can fix this up during the merge.  Fan, other-Paul, are you
>> both okay with the following:
>>
>>    "MAINTAINERS: add IPE entry with Fan Wu as maintainer
>>
>>     Add a MAINTAINERS entry for the Integrity Policy Enforcement (IPE) 
>> LSM."
> 
> Thank you. That is fine by me.
> 
> 
> Kind regards,
> 
> Paul
> 
> 

Hi Paul and Paul,

Thank you both for your feedback and coordination on this. I'm good with 
the proposed changes and appreciate your efforts.

-Fan




  reply	other threads:[~2024-08-07 18:01 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-03  6:08 [PATCH v20 00/20] Integrity Policy Enforcement LSM (IPE) Fan Wu
2024-08-03  6:08 ` [PATCH v20 01/20] security: add ipe lsm Fan Wu
2024-08-03  6:08 ` [PATCH v20 02/20] ipe: add policy parser Fan Wu
2024-08-10 15:50   ` Serge E. Hallyn
2024-08-13 17:54     ` Fan Wu
2024-08-14  1:53       ` Paul Moore
2024-08-14 18:23         ` Fan Wu
2024-08-15 19:11           ` Paul Moore
2024-08-03  6:08 ` [PATCH v20 03/20] ipe: add evaluation loop Fan Wu
2024-08-10 20:05   ` Serge E. Hallyn
2024-08-03  6:08 ` [PATCH v20 04/20] ipe: add LSM hooks on execution and kernel read Fan Wu
2024-08-03  6:08 ` [PATCH v20 05/20] initramfs|security: Add a security hook to do_populate_rootfs() Fan Wu
2024-08-03  6:08 ` [PATCH v20 06/20] ipe: introduce 'boot_verified' as a trust provider Fan Wu
2024-08-03  6:08 ` [PATCH v20 07/20] security: add new securityfs delete function Fan Wu
2024-08-03  6:08 ` [PATCH v20 08/20] ipe: add userspace interface Fan Wu
2024-08-03  6:08 ` [PATCH v20 09/20] uapi|audit|ipe: add ipe auditing support Fan Wu
2024-08-03  6:08 ` [PATCH v20 10/20] ipe: add permissive toggle Fan Wu
2024-08-03  6:08 ` [PATCH v20 11/20] block|lsm: Add LSM blob and new LSM hooks for block devices Fan Wu
2024-08-03  6:08 ` [PATCH v20 12/20] dm verity: expose root hash digest and signature data to LSMs Fan Wu
2024-08-08 22:38   ` Fan Wu
2024-08-15 19:19     ` Paul Moore
2024-08-16 13:35       ` Mikulas Patocka
2024-08-16 19:11         ` Fan Wu
2024-08-18 17:22           ` Paul Moore
2024-08-19 17:47             ` Fan Wu
2024-08-19 19:40               ` Paul Moore
2024-08-03  6:08 ` [PATCH v20 13/20] ipe: add support for dm-verity as a trust provider Fan Wu
2024-08-03  6:08 ` [PATCH v20 14/20] security: add security_inode_setintegrity() hook Fan Wu
2024-08-03  6:08 ` [PATCH v20 15/20] fsverity: expose verified fsverity built-in signatures to LSMs Fan Wu
2024-08-05 18:51   ` Eric Biggers
2024-08-03  6:08 ` [PATCH v20 16/20] ipe: enable support for fs-verity as a trust provider Fan Wu
2024-08-03  6:08 ` [PATCH v20 17/20] scripts: add boot policy generation program Fan Wu
2024-08-03  6:08 ` [PATCH v20 18/20] ipe: kunit test for parser Fan Wu
2024-08-03  6:08 ` [PATCH v20 19/20] Documentation: add ipe documentation Fan Wu
2024-08-03  6:08 ` [PATCH v20 20/20] MAINTAINERS: ipe: add ipe maintainer information Fan Wu
2024-08-03  8:14   ` Paul Menzel
2024-08-06 20:54     ` Paul Moore
2024-08-07  4:48       ` Paul Menzel
2024-08-07 18:01         ` Fan Wu [this message]
2024-08-07 19:42           ` Paul Moore
2024-08-06 20:59 ` [PATCH v20 00/20] Integrity Policy Enforcement LSM (IPE) Paul Moore
2024-08-20  2:51   ` Paul Moore

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=080c93d1-9c02-478f-a0be-f4bd3869c1fd@linux.microsoft.com \
    --to=wufan@linux.microsoft.com \
    --cc=agk@redhat.com \
    --cc=audit@vger.kernel.org \
    --cc=axboe@kernel.dk \
    --cc=corbet@lwn.net \
    --cc=dm-devel@lists.linux.dev \
    --cc=ebiggers@kernel.org \
    --cc=eparis@redhat.com \
    --cc=fsverity@lists.linux.dev \
    --cc=jmorris@namei.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=mpatocka@redhat.com \
    --cc=paul@paul-moore.com \
    --cc=pmenzel@molgen.mpg.de \
    --cc=serge@hallyn.com \
    --cc=snitzer@kernel.org \
    --cc=tytso@mit.edu \
    --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 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).