From: Deven Bowers <deven.desai@linux.microsoft.com>
To: Jann Horn <jannh@google.com>
Cc: agk@redhat.com, Jens Axboe <axboe@kernel.dk>,
snitzer@redhat.com, James Morris <jmorris@namei.org>,
"Serge E. Hallyn" <serge@hallyn.com>,
Mimi Zohar <zohar@linux.ibm.com>,
linux-integrity@vger.kernel.org,
linux-security-module <linux-security-module@vger.kernel.org>,
dm-devel@redhat.com, linux-block@vger.kernel.org,
tyhicks@linux.microsoft.com,
Pavel Tatashin <pasha.tatashin@soleen.com>,
Sasha Levin <sashal@kernel.org>,
jaskarankhurana@linux.microsoft.com, nramas@linux.microsoft.com,
mdsakib@linux.microsoft.com
Subject: Re: [RESEND PATCH 00/11] Integrity Policy Enforcement LSM (IPE)
Date: Mon, 6 Apr 2020 11:59:10 -0700 [thread overview]
Message-ID: <20200406185910.GA77950@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net> (raw)
In-Reply-To: <CAG48ez3JV-tzjRLdcys6Fz9LKYaB1h-1GaeAzkUYtY1RgxsB6g@mail.gmail.com>
On Mon, Apr 06, 2020 at 08:50:46PM +0200, Jann Horn wrote:
> On Mon, Apr 6, 2020 at 8:10 PM <deven.desai@linux.microsoft.com> wrote:
> > Overview:
> > ------------------------------------
> > IPE is a Linux Security Module, which allows for a configurable
> > policy to enforce integrity requirements on the whole system. It
> > attempts to solve the issue of Code Integrity: that any code being
> > executed (or files being read), are identical to the version that
> > was built by a trusted source.
>
> Where's patch 02/11? lore at
> https://lore.kernel.org/linux-security-module/20200406183619.GA77626@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net/T/#t
> has everything other than that patch.
It looks like it's over majordomo's character limit by 7489 characters.
I'll have to repost with this patch broken up. Apologies.
- Deven
next prev parent reply other threads:[~2020-04-06 18:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-06 18:10 [RESEND PATCH 00/11] Integrity Policy Enforcement LSM (IPE) deven.desai
2020-04-06 18:10 ` [RESEND PATCH 01/11] scripts: add ipe tooling to generate boot policy deven.desai
2020-04-06 18:10 ` [RESEND PATCH 03/11] ipe: add property for trust of boot volume deven.desai
2020-04-06 18:10 ` [RESEND PATCH 04/11] fs: add security blob and hooks for block_device deven.desai
2020-04-06 18:10 ` [RESEND PATCH 05/11] dm-verity: move signature check after tree validation deven.desai
2020-04-06 18:10 ` [RESEND PATCH 06/11] dm-verity: add bdev_setsecurity hook for dm-verity signature deven.desai
2020-04-06 18:10 ` [RESEND PATCH 07/11] ipe: add property for signed dmverity volumes deven.desai
2020-04-06 18:10 ` [RESEND PATCH 08/11] dm-verity: add bdev_setsecurity hook for root-hash deven.desai
2020-04-06 18:10 ` [RESEND PATCH 09/11] ipe: add property for dmverity roothash deven.desai
2020-04-06 18:10 ` [RESEND PATCH 10/11] documentation: Add IPE Documentation deven.desai
2020-04-06 18:10 ` [RESEND PATCH 11/11] cleanup: uapi/linux/audit.h deven.desai
2020-04-06 18:36 ` [RESEND PATCH 00/11] Integrity Policy Enforcement LSM (IPE) Deven Bowers
2020-04-06 18:50 ` Jann Horn
2020-04-06 18:59 ` Deven Bowers [this message]
2020-04-06 20:09 ` Sasha Levin
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=20200406185910.GA77950@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net \
--to=deven.desai@linux.microsoft.com \
--cc=agk@redhat.com \
--cc=axboe@kernel.dk \
--cc=dm-devel@redhat.com \
--cc=jannh@google.com \
--cc=jaskarankhurana@linux.microsoft.com \
--cc=jmorris@namei.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mdsakib@linux.microsoft.com \
--cc=nramas@linux.microsoft.com \
--cc=pasha.tatashin@soleen.com \
--cc=sashal@kernel.org \
--cc=serge@hallyn.com \
--cc=snitzer@redhat.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 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).