Add phosphor-image-signing if verify_signature is enabled

The phosphor-image-signing adds the public key to the BMC rootfs
and it was added if the UBI distro was enabled.
The phosphor-software-manager supports signature verification
regardless of the choice of BMC layout, so add it based if the
signature verification config (verify_signture) is enabled.

Otherwise the user would need to know that the package
phosphor-image-signing needed to be added if the signature
verification config was enabled, which is not intuitive. This way
it's done automatically.

Tested: Verified that adding verify_signature resulted in the
        /etc/activationdata/ directory being added to the BMC
        rootfs, and without it no directory was created.

Change-Id: I2c03ab67d925c9b8a7ad0f95bce56b909767cea2
Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
2 files changed
tree: 32d381d227e5fc1853210c11a4506ed16b269c26
  1. aspeed-layer/
  2. classes/
  3. conf/
  4. nuvoton-layer/
  5. raspberrypi/
  6. recipes-connectivity/
  7. recipes-core/
  8. recipes-devtools/
  9. recipes-extended/
  10. recipes-graphics/
  11. recipes-phosphor/
  12. recipes-protocols/
  13. recipes-support/
  14. recipes-textproc/
  15. recipes-x86/
  16. COPYING.apache-2.0
  17. COPYING.MIT
  18. LICENSE
  19. MAINTAINERS
  20. README.md
  21. recipes.txt
README.md

OpenBMC

meta-phosphor is the OpenBMC layer. This layer should be included for all OpenBMC systems. The OpenBMC layer contains content which is shared between all OpenBMC systems.