All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ming Liu" <liu.ming50@gmail.com>
To: yocto@yoctoproject.org
Cc: sergio.prado@toradex.com, akuster808@gmail.com,
	Ming Liu <liu.ming50@gmail.com>
Subject: [meta-security][dunfell][PATCH 6/9] README.md: update according to the refactoring in ima-evm-rootfs.bbclass
Date: Tue,  2 Mar 2021 15:57:42 +0100	[thread overview]
Message-ID: <20210302145745.1891826-7-liu.ming50@gmail.com> (raw)
In-Reply-To: <20210302145745.1891826-1-liu.ming50@gmail.com>

From: Ming Liu <liu.ming50@gmail.com>

Signed-off-by: Ming Liu <liu.ming50@gmail.com>
Signed-off-by: Armin Kuster <akuster808@gmail.com>
---
 meta-integrity/README.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/meta-integrity/README.md b/meta-integrity/README.md
index f08a164..8f525a6 100644
--- a/meta-integrity/README.md
+++ b/meta-integrity/README.md
@@ -69,8 +69,10 @@ Adding the layer only enables IMA (see below regarding EVM) during
 compilation of the Linux kernel. To also activate it when building
 the image, enable image signing in the local.conf like this:
 
-    INHERIT += "ima-evm-rootfs"
+    IMAGE_CLASSES += "ima-evm-rootfs"
     IMA_EVM_KEY_DIR = "${INTEGRITY_BASE}/data/debug-keys"
+    IMA_EVM_PRIVKEY = "${IMA_EVM_KEY_DIR}/privkey_ima.pem"
+    IMA_EVM_X509 = "${IMA_EVM_KEY_DIR}/x509_ima.der"
 
 This uses the default keys provided in the "data" directory of the layer.
 Because everyone has access to these private keys, such an image
-- 
2.29.0


  parent reply	other threads:[~2021-03-02 15:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-02 14:57 [meta-security][dunfell][PATCH 0/9] Some IMA/EVM fixes to dunfell branch Ming Liu
2021-03-02 14:57 ` [meta-security][dunfell][PATCH 1/9] ima-evm-utils: set native REQUIRED_DISTRO_FEATURES to empty Ming Liu
2021-03-02 14:57 ` [meta-security][dunfell][PATCH 2/9] initramfs-framework-ima: fix a wrong path Ming Liu
2021-03-02 14:57 ` [meta-security][dunfell][PATCH 3/9] ima-evm-keys: add recipe Ming Liu
2021-03-02 14:57 ` [meta-security][dunfell][PATCH 4/9] initramfs-framework-ima: RDEPENDS on ima-evm-keys Ming Liu
2021-03-02 14:57 ` [meta-security][dunfell][PATCH 5/9] meta: refactor IMA/EVM sign rootfs Ming Liu
2021-03-02 14:57 ` Ming Liu [this message]
2021-03-02 14:57 ` [meta-security][dunfell][PATCH 7/9] initramfs-framework-ima: let ima_enabled return 0 Ming Liu
2021-03-02 14:57 ` [meta-security][dunfell][PATCH 8/9] ima-evm-rootfs.bbclass: avoid generating /etc/fstab for wic Ming Liu
2021-03-02 14:57 ` [meta-security][dunfell][PATCH 9/9] ima-policy-hashed: add CGROUP2_SUPER_MAGIC fsmagic Ming Liu
2021-03-05  4:54 ` [meta-security][dunfell][PATCH 0/9] Some IMA/EVM fixes to dunfell branch akuster
2021-03-10 10:31   ` Ming Liu
2021-03-10 15:41     ` akuster
2021-03-12  4:49     ` akuster

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=20210302145745.1891826-7-liu.ming50@gmail.com \
    --to=liu.ming50@gmail.com \
    --cc=akuster808@gmail.com \
    --cc=sergio.prado@toradex.com \
    --cc=yocto@yoctoproject.org \
    /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.