Go to file
Thomas Crain bd20964992
[Security] libxml2 CVE patches (#101)
* Patch CVEs in libxml2

* Updates to package manifests

* Remove patch signatures
2020-09-10 18:23:52 -07:00
.github Improve the PR template checklist (#54) 2020-09-02 17:25:52 -07:00
LICENSES-AND-NOTICES Update licenses for the new specs 2020-08-19 01:48:59 +00:00
SPECS [Security] libxml2 CVE patches (#101) 2020-09-10 18:23:52 -07:00
SPECS-SIGNED Add kernel config check logic to the build (#29) 2020-09-03 19:16:38 -07:00
toolkit [Security] libxml2 CVE patches (#101) 2020-09-10 18:23:52 -07:00
.gitignore Ignoring the 'build' and 'out' directories. 2020-08-13 15:37:41 -07:00
CODE_OF_CONDUCT.md Initial CODE_OF_CONDUCT.md commit 2020-07-22 12:27:23 -07:00
CONTRIBUTING.md Initial CBL-Mariner commit to GitHub 2020-08-06 20:17:52 -07:00
LICENSE Initial LICENSE commit 2020-07-22 12:27:24 -07:00
README.md Update trademark section of the readme 2020-09-08 12:59:05 -07:00
SECURITY.md Initial SECURITY.md commit 2020-07-22 12:27:25 -07:00
cgmanifest.json Update etcd to 3.3.25 for CVE fixes (#95) 2020-09-10 18:12:53 -07:00

README.md

CBL-Mariner

CBL-Mariner is an internal Linux distribution for Microsofts cloud infrastructure and edge products and services. CBL-Mariner is designed to provide a consistent platform for these devices and services and will enhance Microsofts ability to stay current on Linux updates. This initiative is part of Microsofts increasing investment in a wide range of Linux technologies, such as SONiC, Azure Sphere OS and Windows Subsystem for Linux (WSL). CBL-Mariner is being shared publicly as part of Microsofts commitment to Open Source and to contribute back to the Linux community. CBL-Mariner is not being offered commercially as a solution for servers, PCs, or IoT devices nor is it included as an IaaS offering. CBL-Mariner does not change our approach or commitment to any existing third-party Linux distribution offerings.

CBL-Mariner has been engineered with the notion that a small common core set of packages can address the universal needs of first party cloud and edge services while allowing individual teams to layer additional packages on top of the common core to produce images for their workloads. This is made possible by a simple build system that enables:

  • Package Generation: This produces the desired set of RPM packages from SPEC files and source files.
  • Image Generation: This produces the desired image artifacts like ISOs or VHDs from a given set of packages.

Whether deployed as a container or a container host, CBL-Mariner consumes limited disk and memory resources. The lightweight characteristics of CBL-Mariner also provides faster boot times and a minimal attack surface. By focusing the features in the core image to just what is needed for our internal cloud customers there are fewer services to load, and fewer attack vectors.

When security vulnerabilities arise, CBL-Mariner supports both a package-based update model and an image based update model. Leveraging the common RPM Package Manager system, CBL-Mariner makes the latest security patches and fixes available for download with the goal of fast turn-around times.

Getting Started with CBL-Mariner:

CBL-Mariner is not released for commercial use, but we understand developers may be interested to examine what we have built. Instructions for building CBL-Mariner may be found here: Toolkit Documentation

Trademarks

This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.

Acknowledgments

Any Linux distribution, including CBL-Mariner, benefits from contributions by the open software community. We gratefully acknowledge all contributions made from the broader open source community, in particular:

  1. The Photon OS Project for SPEC files originating from the Photon distribution.

  2. The Fedora Project for SPEC files, particularly with respect to QT, DNF and several of their dependencies.

  3. GNU and the Free Software Foundation

  4. Linux from Scratch

  5. Openmamba for SPEC files