On 12/19/19 8:36 AM, hu.schlieben@codewrights.de wrote:

Hi,

i'm new here and not really shure this is the right place for this issue.

First you need to enable the distro feature

DISTRO_FEATURES_append = " apparmor"

otherwise the kernel fragments wont be included

I try to get apparmor working using yocto. I tried using thud and zeus with the same result on apparmor_status: apparmor module is not loaded
Checking the kernel flags manually with bitbake -c menuconfig virtual/kernel shows that none of the relevant flags like CONFIG_SECURITY_APPARMOR are set.
Setting these manually i see that the kernel parameters

These you need to append to your kernel commend line. I think it is:
KERNEL_CMDLINE_APPEND_append =

"apparmor=1 security=apparmor" are missing.

My assumption was that adding the apparmor recipe would do all these things.

Actually the recipe should have failed with a DISTRO check message.

I should add that.

This should get you on your way.
- armin

Do i add the recipe somewhere completely wrong?
Do i possibly override apparmor with other recipes?

Any help would be greatly appreciated.

Best regards

hu

Should these

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#47775): https://lists.yoctoproject.org/g/yocto/message/47775
Mute This Topic: https://lists.yoctoproject.org/mt/68834537/1024635
Mute #yocto: https://lists.yoctoproject.org/mk?hashtag=yocto&subid=6691541
Group Owner: yocto+owner@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  [akuster@mvista.com]
-=-=-=-=-=-=-=-=-=-=-=-