tree: d75a705aec532fc6fd078bd1a5b07560b6deee30 [path history] [tgz]
  1. classes/
  2. conf/
  3. docs/
  4. dynamic-layers/
  5. kas/
  6. lib/
  7. meta-hardening/
  8. meta-integrity/
  9. meta-parsec/
  10. meta-tpm/
  11. recipes-compliance/
  12. recipes-core/
  13. recipes-ids/
  14. recipes-kernel/
  15. recipes-mac/
  16. recipes-perl/
  17. recipes-scanners/
  18. recipes-security/
  19. scripts/
  20. wic/
  21. .gitignore
  22. .gitlab-ci.yml


The bbappend files for some recipes (e.g. linux-yocto) in this layer need to have 'security' in DISTRO_FEATURES to have effect. To enable them, add in configuration file the following line.

DISTRO_FEATURES:append = " security"

If meta-security is included, but security is not enabled as a distro feature a warning is printed at parse time:

You have included the meta-security layer, but
'security' has not been enabled in your DISTRO_FEATURES. Some bbappend files
and preferred version setting may not take effect.

If you know what you are doing, this warning can be disabled by setting the following variable in your configuration:


This layer provides security tools, hardening tools for Linux kernels and libraries for implementing security mechanisms.


This layer depends on:

URI: git:// branch: [same one as checked out for this layer]

URI: git:// branch: [same one as checked out for this layer]

Adding the security layer to your build

In order to use this layer, you need to make the build system aware of it.

Assuming the security layer exists at the top-level of your yocto build tree, you can add it to the build system by adding the location of the security layer to bblayers.conf, along with any other layers needed. e.g.:

/path/to/layer/meta-security "

Optional Dynamic layer dependancy

URI: git://

URI: git://

URI: git://

BBLAYERS += "/path/to/layer/meta-openembedded/meta-oe" BBLAYERS += "/path/to/layer/meta-openembedded/meta-perl" BBLAYERS += "/path/to/layer/meta-openembedded/meta-python"

This will activate the dynamic-layer mechanism.


Send pull requests, patches, comments or questions to

When sending single patches, please using something like: 'git send-email -1 --to --subject-prefix=meta-security][PATCH'

These values can be set as defaults for this repository:

$ git config $ git config format.subjectPrefix meta-security][PATCH

Now you can just do 'git send-email origin/master' to send all local patches.

For pull requests, please use create-pull-request and send-pull-request.

Maintainers: Armin Kuster


All metadata is MIT licensed unless otherwise stated. Source code included in tree for individual recipes is under the LICENSE stated in each recipe (.bb file) unless otherwise stated.