Name
Date
Size
#Lines
LOC

..--

classes/H--309253

conf/H--9076

docs/H--482335

dynamic-layers/H--10,6396,893

kas/H--269207

lib/oeqa/H--839650

meta-hardening/H--251155

meta-integrity/H--1,250940

meta-parsec/H--1,7241,504

meta-tpm/H--2,9382,388

recipes-compliance/H--254186

recipes-core/H--364283

recipes-ids/H--7,0865,331

recipes-kernel/H--6242

recipes-mac/H--1,386999

recipes-perl/perl/H--143114

recipes-scanners/H--2,083847

recipes-security/H--3,4462,758

scripts/H--3521

wic/H--5442

.gitignoreH A D16-Oct-202043 87

.gitlab-ci.ymlH A D03-Feb-20253 KiB123104

COPYING.MITH A D14-Aug-20181,023 1815

README.mdH A D03-Feb-20253.2 KiB10063

README.md

1Master-next:
2[![pipeline status](https://gitlab.com/akuster/meta-security/badges/master-next/pipeline.svg)](https://gitlab.com/akuster/meta-security/-/commits/master-next)
3
4Master: [![pipeline status](https://gitlab.com/akuster/meta-security/badges/master/pipeline.svg)](https://gitlab.com/akuster/meta-security/-/commits/master)
5
6Meta-security
7=============
8
9The bbappend files for some recipes (e.g. linux-yocto) in this layer need
10to have 'security' in DISTRO_FEATURES to have effect.
11To enable them, add in configuration file the following line.
12
13  DISTRO_FEATURES:append = " security"
14
15If meta-security is included, but security  is not enabled as a
16distro feature a warning is printed at parse time:
17
18    You have included the meta-security layer, but
19    'security' has not been enabled in your DISTRO_FEATURES. Some bbappend files
20    and preferred version setting may not take effect.
21
22If you know what you are doing, this warning can be disabled by setting the following
23variable in your configuration:
24
25  SKIP_META_SECURITY_SANITY_CHECK = 1
26
27This layer provides security tools, hardening tools for Linux kernels
28and libraries for implementing security mechanisms.
29
30Dependencies
31============
32
33This layer depends on:
34
35  URI: git://git.openembedded.org/openembedded-core
36  branch: [same one as checked out for this layer]
37
38  URI: git://git.openembedded.org/meta-openembedded/meta-oe
39  branch: [same one as checked out for this layer]
40
41Adding the security layer to your build
42========================================
43
44In order to use this layer, you need to make the build system aware of
45it.
46
47Assuming the security layer exists at the top-level of your
48yocto build tree, you can add it to the build system by adding the
49location of the security layer to bblayers.conf, along with any
50other layers needed. e.g.:
51
52  BBLAYERS ?= " \
53    /path/to/oe-core/meta \
54    /path/to/meta-openembedded/meta-oe \
55    /path/to/layer/meta-security "
56
57Optional Dynamic layer dependancy
58======================================
59
60  URI: git://git.openembedded.org/meta-openembedded/meta-oe
61
62  URI: git://git.openembedded.org/meta-openembedded/meta-perl
63
64  URI: git://git.openembedded.org/meta-openembedded/meta-python
65
66  BBLAYERS += "/path/to/layer/meta-openembedded/meta-oe"
67  BBLAYERS += "/path/to/layer/meta-openembedded/meta-perl"
68  BBLAYERS += "/path/to/layer/meta-openembedded/meta-python"
69
70This will activate the dynamic-layer mechanism.
71
72
73
74Maintenance
75======================================
76
77Send pull requests, patches, comments or questions to yocto-patches@lists.yoctoproject.org
78
79When sending single patches, please using something like:
80'git send-email -1 --to yocto-patches@lists.yoctoproject.org --subject-prefix=meta-security][PATCH'
81
82These values can be set as defaults for this repository:
83
84$ git config sendemail.to yocto-patches@lists.yoctoproject.org
85$ git config format.subjectPrefix meta-security][PATCH
86
87Now you can just do 'git send-email origin/master' to send all local patches.
88
89For pull requests, please use create-pull-request and send-pull-request.
90
91Maintainers:    Armin Kuster <akuster808@gmail.com>
92
93
94License
95=======
96
97All metadata is MIT licensed unless otherwise stated. Source code included
98in tree for individual recipes is under the LICENSE stated in each recipe
99(.bb file) unless otherwise stated.
100