mirror of
git://git.openembedded.org/meta-openembedded
synced 2026-06-09 23:19:09 +00:00
7526541209
This way yocto cve-check can find open CVE's. See also: http://lists.openembedded.org/pipermail/openembedded-core/2017-July/139897.html "Results from cve-check are not very good at the moment. One of the reasons for this is that component names used in CVE database differ from yocto recipe names. This series fixes several of those name mapping problems by setting the CVE_PRODUCT correctly in the recipes. To check this mapping with after a build, I'm exporting LICENSE and CVE_PRODUCT variables to buildhistory for recipes and packages." Value added is based on: https://nvd.nist.gov/products/cpe/search/results?keyword=netcat&status=FINAL&orderBy=CPEURI&namingFormat=2.3 Signed-off-by: Andre Carvalho <andrestc@fb.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
meta-networking
===============
This layer is intended to be a central point for networking-related
packages and configuration. It should be useful directly on top of
oe-core and compliments meta-openembedded. It should be primarily useful
to the following groups:
- Anyone building a small networking device (eg. a home router /
bridge / switch).
- Anyone wanting to add network services to their device (eg.
anything that might benefit from a small ftp/tftp server)
Dependencies
------------
This layer depends on:
URI: git://github.com/openembedded/openembedded-core.git
branch: master
revision: HEAD
For some recipes, the meta-oe layer is required:
URI: git://github.com/openembedded/meta-openembedded.git
subdirectory: meta-oe
branch: master
revision: HEAD
URI: git://github.com/openembedded/meta-openembedded.git
subdirectory: meta-python
branch: master
revision: HEAD
Maintenance
-----------
Please see the MAINTAINERS file for information on contacting the
maintainers of this layer, as well as instructions for submitting patches.