yocto2.6: update openssl options

It's unclear why, but yocto 2.6 seems to be checking our options
settings for correctness.  We seem to have typos on one option
"no-engine" vs "no-engines".  Unfortunately python-cryptography expodes
in spectacular fashion if we _actually_ disable engines, so simply
delete the option for now.

We also have options that don't exist, like ripemd160.  Remove the
non-existing options.

Change-Id: Ie20aab41844ed6af95cb53e9f89243419c51f471
Signed-off-by: Ed Tanous <ed.tanous@intel.com>
1 file changed
tree: deb4dd0f7adf443cb289c263210349a7ce3680cc
  1. aspeed-layer/
  2. classes/
  3. conf/
  4. nuvoton-layer/
  5. recipes-connectivity/
  6. recipes-core/
  7. recipes-devtools/
  8. recipes-extended/
  9. recipes-phosphor/
  10. recipes-protocols/
  11. recipes-support/
  12. recipes-textproc/
  13. COPYING.apache-2.0
  14. COPYING.MIT
  15. LICENSE
  16. MAINTAINERS
  17. README.md
  18. 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.