Digi
/
meta-digi
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
meta-digi/meta-digi-dey
History
Gabriel Valcazar 171e5a5db1 trustfence.bbclass: copy public key to fs only if TRUSTFENCE_SIGN is enabled 
Commit 998598415a moved this logic to the
trustfence.bbclass file, but in doing so, it removed the TRUSTFENCE_SIGN check
it used to have. The check is needed for two reasons:

* The signing of SWU packages only occurs when TRUSTFENCE_SIGN is enabled, so
  there's no need to copy the key if it's disabled
* When building a project from scratch that has Trustfence enabled but
  TRUSTFENCE_SIGN disabled, a PKI is never generated and the key doesn't exist.
  Because of this, the key won't be found and an error will occur. Note that
  if your project is already pointing to a populated PKI, the error won't
  happen, only if there's no PKI to begin with.

Although the PKI is guaranteed to exist by the time the rootfs is populated,
make sure to check that it has been properly generated and create it if it
doesn't exist. This logic depends on the trustfence-gen-pki.sh from
trustfence-sign-tools-native, so add it as a dependency for
dey-image-recovery-initramfs. The dependency is already there for another
feature in the dey-image recipes, so simply reflect this new dependency in a
comment.

Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
(cherry picked from commit 8e52c27d5a8e8071c3a17754e91c1819bcceee15)
 		2024-11-14 13:30:03 +01:00
..
classes trustfence.bbclass: copy public key to fs only if TRUSTFENCE_SIGN is enabled 2024-11-14 13:30:03 +01:00
conf meta-digi-dey: layer.conf: make "outdated" layers compatible with Yocto 5.0 2024-10-17 13:03:37 +02:00
dynamic-layers ccimx93: update ML package for NXP release 6.6.36-2.1.0 2024-11-05 18:17:02 +01:00
recipes-aws Update Digi Copyright header 2024-07-15 09:28:58 +02:00
recipes-connectivity bluetooth-init: ccimx6ul: validate FW was correctly loaded 2024-10-31 09:59:42 +01:00
recipes-core trustfence.bbclass: copy public key to fs only if TRUSTFENCE_SIGN is enabled 2024-11-14 13:30:03 +01:00
recipes-crank Update Digi Copyright header 2024-07-15 09:28:58 +02:00
recipes-devtools Revert "orc: fix native build on ubuntu 18" 2024-11-11 11:35:27 +01:00
recipes-digi meta-digi-dey: sysinfo: fix build info filename from "build" to "buildinfo" 2024-11-07 12:33:07 +01:00
recipes-extended dey: cosmetic, mark patches as DEY specific 2024-10-22 15:48:00 +02:00
recipes-gnome Update Digi Copyright header 2024-07-15 09:28:58 +02:00
recipes-graphics dey: cosmetic, mark patches as DEY specific 2024-10-22 15:48:00 +02:00
recipes-multimedia dey: cosmetic, mark patches as DEY specific 2024-10-22 15:48:00 +02:00
recipes-sato Update Digi Copyright header 2024-07-15 09:28:58 +02:00
recipes-support dey: cosmetic, mark patches as DEY specific 2024-10-22 15:48:00 +02:00
DIGI_EULA DIGI_EULA: Update Digi EULA file. 2017-08-29 12:23:22 +02:00
DIGI_OPEN_EULA meta-digi: Rename from DEL to DEY. 2013-06-12 13:18:37 +02:00
README meta-digi: update support email address 2017-10-30 17:02:33 +01:00

README 

OpenEmbedded/Yocto Digi Embedded Linux layer
============================================

This layer provides the Digi Embedded Linux distribution images.

This layer depends on:

git://git.yoctoproject.org/poky.git
git://git.openembedded.org/meta-openembedded.git
git://git.yoctoproject.org/meta-freescale.git
git://github.com/Freescale/meta-fsl-demos.git

Digi's license agreements
-------------------------

All software is covered by Digi's general EULA and Digi's Open Source
EULA. To have the right to use the software in your images you need to
read and accept both EULAs at the DIGI_EULA and DIGI_OPEN_EULA files.

NXP Semiconductors' software license agreement
----------------------------------------------

Some platforms depends on libraries and packages that are covered by
NXP Semiconductors' EULA. To have the right to use those binaries in
your images you need to read and accept the EULA file in meta-freescale
Yocto layer.

Support
-------

This layer is provided 'as is' with no guarantee. However, some support
may be available from tech.support@digi.com