From: James Morris <jmorris@namei.org>
To: James Morse <james.morse@arm.com>
Cc: prsriva <prsriva@linux.microsoft.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-integrity@vger.kernel.org, kexec@lists.infradead.org,
mark.rutland@arm.com, jean-philippe@linaro.org, arnd@arndb.de,
takahiro.akashi@linaro.org, sboyd@kernel.org,
catalin.marinas@arm.com, zohar@linux.ibm.com,
yamada.masahiro@socionext.com, duwe@lst.de,
bauerman@linux.ibm.com, tglx@linutronix.de, allison@lohutok.net,
ard.biesheuvel@linaro.org
Subject: Re: [PATCH V4 0/2] Add support for arm64 to carry ima measurement
Date: Wed, 16 Oct 2019 09:15:39 +1100 (AEDT) [thread overview]
Message-ID: <alpine.LRH.2.21.1910160914090.11167@namei.org> (raw)
In-Reply-To: <0053eb68-0905-4679-c97a-00c5cb6f1abb@arm.com>
On Tue, 15 Oct 2019, James Morse wrote:
> > The IMA logs are event logs for module load time signature validation(based on policies)
> > which are backed by the TPM. No SecureBoot information is present in the log other than
> > the boot aggregate.
>
> Okay, so SecureBoot is optional with this thing.
Correct. Verified boot is one alternative.
--
James Morris
<jmorris@namei.org>
next prev parent reply other threads:[~2019-10-15 22:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-11 0:35 [PATCH V4 0/2] Add support for arm64 to carry ima measurement Prakhar Srivastava
2019-10-11 0:35 ` [PATCH V4 1/2] Add support for arm64 to carry ima measurement log in kexec_file_load Prakhar Srivastava
2019-10-11 0:36 ` [PATCH V4 2/2] update powerpc implementation to call into of_ima* Prakhar Srivastava
2019-10-14 18:02 ` [PATCH V4 0/2] Add support for arm64 to carry ima measurement James Morse
2019-10-15 1:31 ` prsriva
2019-10-15 17:39 ` James Morse
2019-10-15 18:47 ` Pavel Tatashin
2019-10-21 17:38 ` prsriva
2019-10-25 17:08 ` James Morse
2019-10-15 22:15 ` James Morris [this message]
2019-10-16 1:44 ` Mimi Zohar
2019-10-25 17:07 ` James Morse
2019-10-25 17:39 ` Mimi Zohar
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=alpine.LRH.2.21.1910160914090.11167@namei.org \
--to=jmorris@namei.org \
--cc=allison@lohutok.net \
--cc=ard.biesheuvel@linaro.org \
--cc=arnd@arndb.de \
--cc=bauerman@linux.ibm.com \
--cc=catalin.marinas@arm.com \
--cc=duwe@lst.de \
--cc=james.morse@arm.com \
--cc=jean-philippe@linaro.org \
--cc=kexec@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=prsriva@linux.microsoft.com \
--cc=sboyd@kernel.org \
--cc=takahiro.akashi@linaro.org \
--cc=tglx@linutronix.de \
--cc=yamada.masahiro@socionext.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).