Gitiles
Code Review Sign In
gerrit.openbmc.org / mdmillerii / openbmc / 2ee96f54765655f3a7b850c2b9fb4db27a2411de
commit2ee96f54765655f3a7b850c2b9fb4db27a2411de[log] [tgz]
authorEd Tanous <ed.tanous@intel.com>Fri Sep 07 10:18:44 2018 -0700
committerBrad Bishop <bradleyb@fuzziesquirrel.com>Tue Sep 11 21:33:51 2018 -0400
tree11b3af2eb6a978ed9ddda1ab1b2b493aab2d1ff3
parent9392c69cb94f33ad32d35e907d14da19eeb88986 [diff]
Allow use of insecure hashes in openssl-native

Because of this commit here:
https://github.com/webpack/webpack/pull/6549/commits

The newest version of webpack chooses to use md4 for compile time
hashing instead of something more useful like md5/sha1/sha256.  In the
openbmc openssl.bbappend, we override and disable some of the ciphers we
should not be using on target.

This patchset adjusts the recipe to only disable the insecure hashes on
the target, so openssl-native still compiles and allows them.

This patchset is the first in a series to upgrade phosphor-webui to the
latest versions of the packages we use.

Originally opened as:
https://gerrit.openbmc-project.xyz/#/c/openbmc/openbmc/+/12561/

(From meta-phosphor rev: e5217200adeed14222afde2b3ff6b972173a938f)

Change-Id: Ic68b8cb9f2277cfca78f75aac0640b363640c61d
Signed-off-by: Ed Tanous <ed.tanous@intel.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
1 file changed
tree: 11b3af2eb6a978ed9ddda1ab1b2b493aab2d1ff3
  1. meta-arm/
  2. meta-aspeed/
  3. meta-evb/
  4. meta-ibm/
  5. meta-ingrasys/
  6. meta-intel/
  7. meta-inventec/
  8. meta-mellanox/
  9. meta-nuvoton/
  10. meta-openembedded/
  11. meta-openpower/
  12. meta-phosphor/
  13. meta-portwell/
  14. meta-qualcomm/
  15. meta-quanta/
  16. meta-raspberrypi/
  17. meta-security/
  18. meta-x86/
  19. poky/
  20. bitbake ⇨ poky/bitbake/
  21. LICENSE ⇨ poky/LICENSE
  22. meta ⇨ poky/meta
  23. meta-poky ⇨ poky/meta-poky/
  24. oe-init-build-env ⇨ poky/oe-init-build-env
  25. scripts ⇨ poky/scripts/
  26. .gitignore
  27. .gitreview
  28. .templateconf
  29. MAINTAINERS
  30. openbmc-env
  31. README.md
  32. setup
README.md

OpenBMC

Build Status

The OpenBMC project can be described as a Linux distribution for embedded devices that have a BMC; typically, but not limited to, things like servers, top of rack switches or RAID appliances. The OpenBMC stack uses technologies such as Yocto, OpenEmbedded, systemd, and D-Bus to allow easy customization for your server platform.

Setting up your OpenBMC project

1) Prerequisite

  • Ubuntu 14.04
sudo apt-get install -y git build-essential libsdl1.2-dev texinfo gawk chrpath diffstat
  • Fedora 23
sudo dnf install -y git patch diffstat texinfo chrpath SDL-devel bitbake
sudo dnf groupinstall "C Development Tools and Libraries"

2) Download the source

git clone git@github.com:openbmc/openbmc.git
cd openbmc

3) Target your hardware

Any build requires an environment variable known as TEMPLATECONF to be set to a hardware target. You can see all of the known targets with find meta-* -name local.conf.sample. Choose the hardware target and then move to the next step. Additional examples can be found in the OpenBMC Cheatsheet

MachineTEMPLATECONF
Palmettometa-ibm/meta-palmetto/conf
Zaiusmeta-ingrasys/meta-zaius/conf
Witherspoonmeta-ibm/meta-witherspoon/conf

As an example target Palmetto

export TEMPLATECONF=meta-ibm/meta-palmetto/conf

4) Build

. openbmc-env
bitbake obmc-phosphor-image

Additional details can be found in the docs repository.

Build Validation and Testing

Commits submitted by members of the OpenBMC GitHub community are compiled and tested via our Jenkins server. Commits are run through two levels of testing. At the repository level the makefile make check directive is run. At the system level, the commit is built into a firmware image and run with an arm-softmmu QEMU model against a barrage of CI tests.

Commits submitted by non-members do not automatically proceed through CI testing. After visual inspection of the commit, a CI run can be manually performed by the reviewer.

Automated testing against the QEMU model along with supported systems are performed. The OpenBMC project uses the Robot Framework for all automation. Our complete test repository can be found here.

Submitting Patches

Support of additional hardware and software packages is always welcome. Please follow the contributing guidelines when making a submission. It is expected that contributions contain test cases.

Bug Reporting

Issues are managed on GitHub. It is recommended you search through the issues before opening a new one.

Features of OpenBMC

Feature List

  • REST Management
  • IPMI
  • SSH based SOL
  • Power and Cooling Management
  • Event Logs
  • Zeroconf discoverable
  • Sensors
  • Inventory
  • LED Management
  • Host Watchdog
  • Simulation
  • Code Update Support for multiple BMC/BIOS images
  • POWER On Chip Controller (OCC) Support

Features In Progress

  • Full IPMI 2.0 Compliance with DCMI
  • Verified Boot
  • HTML5 Java Script Web User Interface
  • BMC RAS

Features Requested but need help

  • OpenCompute Redfish Compliance
  • OpenBMC performance monitoring
  • cgroup user management and policies
  • Remote KVM
  • Remote USB
  • OpenStack Ironic Integration
  • QEMU enhancements

Finding out more

Dive deeper in to OpenBMC by opening the docs repository.

Contact