Yocto Project Discussions
 help / color / mirror / Atom feed
From: "Armpit" <akuster808@gmail.com>
To: hu.schlieben@codewrights.de, yocto@lists.yoctoproject.org
Subject: Re: [yocto] apparmor setup #yocto
Date: Thu, 19 Dec 2019 14:16:48 -0800	[thread overview]
Message-ID: <ee9e3ff4-6209-465a-b5d1-10072dbbfe92@gmail.com> (raw)
In-Reply-To: <lyds.1576773373989526666.E1JI@lists.yoctoproject.org>

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

      reply	other threads:[~2019-12-19 22:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-19 16:36 apparmor setup #yocto hu.schlieben
2019-12-19 22:16 ` Armpit [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ee9e3ff4-6209-465a-b5d1-10072dbbfe92@gmail.com \
    --to=akuster808@gmail.com \
    --cc=hu.schlieben@codewrights.de \
    --cc=yocto@lists.yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox