From: Andreas Oberritter <obi@opendreambox.org>
To: openembedded-core@lists.openembedded.org
Subject: Re: [RFC][PATCH v2 1/4] u-boot: basic support of dtb append for verified boot
Date: Thu, 21 Apr 2016 16:06:29 +0200 [thread overview]
Message-ID: <5718DE65.1070402@opendreambox.org> (raw)
In-Reply-To: <1461160239-7799-2-git-send-email-yannick.gicquel@iot.bzh>
On 20.04.2016 15:50, Yannick Gicquel wrote:
> This introduces a new uboot-sign.class to support U-Boot verified boot.
>
> This part delivers the new class file, with related environment variables, and
> a basic prepend to do_install task which performs the concatenation of the
> u-boot-nodtb.bin and the device tree blob. The 'cat' command used
> overrides the u-boot.bin in both DEPLOYDIR & build dir to propagate the
> changes in later tasks (do_install, do_package, etc.)
>
> Signed-off-by: Yannick Gicquel <yannick.gicquel@iot.bzh>
> ---
> meta/classes/uboot-sign.bbclass | 59 ++++++++++++++++++++++++++++++++++++++
> meta/recipes-bsp/u-boot/u-boot.inc | 2 +-
> 2 files changed, 60 insertions(+), 1 deletion(-)
> create mode 100644 meta/classes/uboot-sign.bbclass
>
> diff --git a/meta/classes/uboot-sign.bbclass b/meta/classes/uboot-sign.bbclass
> new file mode 100644
> index 0000000..63a5181
> --- /dev/null
> +++ b/meta/classes/uboot-sign.bbclass
> @@ -0,0 +1,59 @@
> +# This file is part of U-Boot verified boot support and is intended to be
> +# inherited from u-boot recipe and from kernel-fitimage.bbclass.
> +#
> +# The signature procedure requires the user to generate an RSA key and
> +# certificate in a directory and to define the following variable:
> +#
> +# UBOOT_SIGN_KEYDIR = "/keys/directory"
> +# UBOOT_SIGN_KEYNAME = "dev" # keys name in keydir (eg. "dev.crt", "dev.key")
> +# UBOOT_MKIMAGE_DTCOPTS = "-I dts -O dtb -p 2000"
> +# UBOOT_SIGN_ENABLE = "1"
> +#
> +# As verified boot depends on fitImage generation, following is also required:
> +#
> +# KERNEL_CLASSES ?= " kernel-fitimage "
> +# KERNEL_IMAGETYPE ?= "fitImage"
> +#
> +# The signature support is limited to the use of CONFIG_OF_SEPARATE in U-Boot.
> +#
> +# The tasks sequence is as below, using DEPLOY_IMAGE_DIR as common place to
> +# treat the device tree blob:
> +#
> +# u-boot:do_deploy -> virtual/kernel:do_assemble_fitimage -> u-boot:do_install
> +#
> +# For more details on signature process, please refer to U-boot documentation.
> +
> +# Signature activation.
> +UBOOT_SIGN_ENABLE ?= "0"
> +
> +# Default value for deployment filenames.
> +UBOOT_DTB_IMAGE ?= "u-boot-${MACHINE}-${PV}-${PR}.dtb"
> +UBOOT_DTB_BINARY ?= "u-boot.dtb"
> +UBOOT_DTB_SYMLINK ?= "u-boot-${MACHINE}.dtb"
> +UBOOT_NODTB_IMAGE ?= "u-boot-nodtb-${MACHINE}-${PV}-${PR}.${UBOOT_SUFFIX}"
> +UBOOT_NODTB_BINARY ?= "u-boot-nodtb.${UBOOT_SUFFIX}"
> +UBOOT_NODTB_SYMLINK ?= "u-boot-nodtb-${MACHINE}.${UBOOT_SUFFIX}"
> +
I think you should split the file at this point and either put the lines
above into uboot-sign-base.bbclass and include it from here or put the
lines below into u-boot.inc directly. This way you don't add unnecessary
code for u-boot to kernel recipes, and lose the dependency on PN =
"u-boot" at the same time.
Regards,
Andreas
> +#
> +# Following is relevant only for u-boot recipes:
> +#
> +
> +do_install_prepend_pn-u-boot () {
> + # Concatenate U-Boot w/o DTB & DTB with public key
> + # (cf. kernel-fitimage.bbclass for more details)
> + cd ${DEPLOYDIR}
> + if [ "x${UBOOT_SIGN_ENABLE}" = "x1" ]; then
> + if [ -e "${UBOOT_NODTB_IMAGE}" -a -e "${UBOOT_DTB_IMAGE}" ]; then
> + cat ${UBOOT_NODTB_IMAGE} ${UBOOT_DTB_IMAGE} > ${UBOOT_IMAGE}
> + cat ${UBOOT_NODTB_IMAGE} ${UBOOT_DTB_IMAGE} > ${B}/${UBOOT_BINARY}
> + else
> + bbwarn "Failure while adding public key to u-boot binary. Verified boot won't be available."
> + fi
> + fi
> +}
> +
> +python () {
> + if d.getVar('UBOOT_SIGN_ENABLE', True) == '1' and d.getVar('PN', True) == 'u-boot':
> + kernel_pn = d.getVar('PREFERRED_PROVIDER_virtual/kernel', True)
> + d.appendVarFlag('do_install', 'depends', ' %s:do_assemble_fitimage' % kernel_pn)
> +}
> diff --git a/meta/recipes-bsp/u-boot/u-boot.inc b/meta/recipes-bsp/u-boot/u-boot.inc
> index 3ba866d..037f35c 100644
> --- a/meta/recipes-bsp/u-boot/u-boot.inc
> +++ b/meta/recipes-bsp/u-boot/u-boot.inc
> @@ -12,7 +12,7 @@ S = "${WORKDIR}/git"
>
> PACKAGE_ARCH = "${MACHINE_ARCH}"
>
> -inherit uboot-config deploy
> +inherit uboot-config uboot-sign deploy
>
> EXTRA_OEMAKE = 'CROSS_COMPILE=${TARGET_PREFIX} CC="${TARGET_PREFIX}gcc ${TOOLCHAIN_OPTIONS}" V=1'
> EXTRA_OEMAKE += 'HOSTCC="${BUILD_CC} ${BUILD_CFLAGS} ${BUILD_LDFLAGS}"'
>
next prev parent reply other threads:[~2016-04-21 14:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-20 13:50 [RFC][PATCH v2 0/4] U-Boot verified boot basic support Yannick Gicquel
2016-04-20 13:50 ` [RFC][PATCH v2 1/4] u-boot: basic support of dtb append for verified boot Yannick Gicquel
2016-04-20 15:23 ` Tom Rini
2016-04-20 19:33 ` [RFC, v2, " Andreas Dannenberg
2016-04-20 19:49 ` [RFC][PATCH v2 " Denys Dmytriyenko
2016-04-20 21:03 ` Tom Rini
2016-04-21 10:25 ` Yannick GICQUEL
2016-04-21 14:06 ` Andreas Oberritter [this message]
2016-04-21 19:55 ` Yannick GICQUEL
2016-04-24 12:56 ` Bernhard Reutner-Fischer
2016-04-20 13:50 ` [RFC][PATCH v2 2/4] u-boot: deploy u-boot-nodtb and dtb files Yannick Gicquel
2016-04-20 15:23 ` Tom Rini
2016-04-20 19:34 ` [RFC, v2, " Andreas Dannenberg
2016-04-20 19:51 ` [RFC][PATCH v2 " Denys Dmytriyenko
2016-04-20 13:50 ` [RFC][PATCH v2 3/4] kernel: fitimage: support device tree compiler options Yannick Gicquel
2016-04-20 15:23 ` Tom Rini
2016-04-20 19:34 ` [RFC, v2, " Andreas Dannenberg
2016-04-20 13:50 ` [RFC][PATCH v2 4/4] kernel: fitimage: basic support for fitimage signature Yannick Gicquel
2016-04-20 15:23 ` Tom Rini
2016-04-20 19:35 ` [RFC, v2, " Andreas Dannenberg
2016-04-20 15:23 ` [RFC][PATCH v2 0/4] U-Boot verified boot basic support Tom Rini
2016-04-20 19:43 ` Denys Dmytriyenko
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=5718DE65.1070402@opendreambox.org \
--to=obi@opendreambox.org \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox