| commit | 0a97a5d7175e5dfe81609b7a539e1319514d2f7a | [log] [tgz] |
|---|---|---|
| author | Joseph Reynolds <jrey@us.ibm.com> | Mon Jul 16 16:12:02 2018 -0500 |
| committer | Gunnar Mills <gmills@us.ibm.com> | Mon Oct 29 14:25:28 2018 +0000 |
| tree | e2bfa9d058ab87844fd6b728ca3decbebb6e295a | |
| parent | 5b4f5d6b242391c43fe979b895a31c3820a967b2 [diff] |
Create security vulnerability reporting mechanism This documents the process to privately report OpenBMC security vulnerabilities with the intention of giving time to the project to fix the problem before public disclosure. This first commit establishes the project's scope. The next commit: - provides guidelines to the OpenBMC security response team as it works to address the security issues and disclose publicly - establishes the "How to report security vulnerabilities" web page to tell problem submitters what to include in their report and what to expect from the OpenBMC security response team Change-Id: Ib90070f998a815ba3f4430c7eb6ff84b3934e012 Signed-off-by: Joseph Reynolds <jrey@us.ibm.com>
This repository contains documentation for OpenBMC as a whole. There may be component-specific documentation in the repository for each component.
These documents describe how to use OpenBMC, including using the programmatic interfaces to an OpenBMC system.
rest-api.md: Introduction to using the OpenBMC REST API
console.md: Using the host console
host-management.md: Performing host management tasks with OpenBMC
code-update: Updating OpenBMC and host platform firmware
These documents contain details on developing OpenBMC code itself
cheatsheet.md: Quick reference for some common development tasks
CONTRIBUTING.md: Guidelines for contributing to OpenBMC
kernel-development.md: Reference for common kernel development tasks
REST-cheatsheet.md: Quick reference for some common curl commands usage.
The OpenBMC project's aim is to create a highly extensible framework for BMC software and implement for data-center computer systems.
We have a few high-level objectives:
The OpenBMC framework must be extensible, easy to learn, and usable in a variety of programming languages.
Provide a REST API for external management, and allow for "pluggable" interfaces for other types of management interactions.
Provide a remote host console, accessible over the network
Persist network configuration settable from REST interface and host
Provide a robust solution for RTC management, exposed to the host.
Compatible with host firmware implementations for basic IPMI communication between host and BMC
Provide a flexible and hierarchical inventory tracking component
Maintain a sensor database and track thresholds