blob: eb15366753cdf0330d3837333c7c9b8f490dca37 [file] [log] [blame]
This layer provides security tools, hardening tools for Linux kernels
and libraries for implementing security mechanisms.
This layer depends on:
URI: git://
branch: master
URI: git://
branch: master
URI: git://
branch: master
URI: git://
branch: master
URI: git://
branch: master
Adding the security layer to your build
In order to use this layer, you need to make the build system aware of
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/oe-core/meta \
/path/to/meta-openembedded/meta-oe \
/path/to/meta-openembedded/meta-perl \
/path/to/meta-openembedded/meta-python \
/path/to/meta-openembedded/meta-networking \
/path/to/layer/meta-security "
Optional Rust dependancy
If you want to use the latest Suricata that needs rust, you will need to clone
branch: master
BBLAYERS += "/path/to/layer/meta-rust"
This will activate the dynamic-layer mechanism and pull in the newer suricata
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.