Yocto Project Discussions
 help / color / mirror / Atom feed
* apparmor setup #yocto
@ 2019-12-19 16:36 hu.schlieben
  2019-12-19 22:16 ` [yocto] " Armpit
  0 siblings, 1 reply; 2+ messages in thread
From: hu.schlieben @ 2019-12-19 16:36 UTC (permalink / raw)
  To: yocto

[-- Attachment #1: Type: text/plain, Size: 750 bytes --]

Hi,

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

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 " apparmor=1 security=apparmor" are missing.

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

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

[-- Attachment #2: Type: text/html, Size: 1177 bytes --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [yocto] apparmor setup #yocto
  2019-12-19 16:36 apparmor setup #yocto hu.schlieben
@ 2019-12-19 22:16 ` Armpit
  0 siblings, 0 replies; 2+ messages in thread
From: Armpit @ 2019-12-19 22:16 UTC (permalink / raw)
  To: hu.schlieben, yocto

[-- Attachment #1: Type: text/plain, Size: 1772 bytes --]



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]
> -=-=-=-=-=-=-=-=-=-=-=-


[-- Attachment #2: Type: text/html, Size: 4008 bytes --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2019-12-19 22:16 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2019-12-19 16:36 apparmor setup #yocto hu.schlieben
2019-12-19 22:16 ` [yocto] " Armpit

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox