openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Ratan Gupta <ratankgupta31@gmail.com>
To: openbmc@lists.ozlabs.org
Subject: Re: apparmor support
Date: Thu, 5 Aug 2021 08:26:03 +0530	[thread overview]
Message-ID: <CAMhqiMr+b_=bJ=JwuSZUa8eooYVfcEoM7crAgKNH9v6cb2PWOw@mail.gmail.com> (raw)
In-Reply-To: <CAMhqiMofyc2mGBYYJUXftj2kbQzmZt=q0pwyk2KPoSVxrHVKBQ@mail.gmail.com>

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

Hi Team,

Does anybody have any experience in writing the apparmor profile and
confine some of the openbmc application? I pulled the apparmor in the
openbmc image but it is not confining the openbmc application.Confining the
application on ubuntu works fine but that is not true with openbmc.

I am chasing this issue with apparmor team through
https://gitlab.com/apparmor/apparmor/-/issues/183

Ratan

On Tue, Jul 27, 2021 at 1:27 PM Ratan Gupta <ratankgupta31@gmail.com> wrote:

> Ignore my previous email, I got the issue that CONFIG_SECURITY should have
> been enabled also(That is a dependency)
>
> https://github.com/openbmc/linux/blob/1519240139a91e3dbc97d8f79de29a22a3328257/security/apparmor/Kconfig#L4
>
> On Tue, Jul 27, 2021 at 11:42 AM Ratan Gupta <ratankgupta31@gmail.com>
> wrote:
>
>> Hi All,
>>
>> I was trying to pull apparmor in openbmc, all the user space application
>> got pulled however I was unable to build the kernel with apparmor support.
>>
>> I made the following kernel configuration to include the apparmor(
>> https://github.com/openbmc/linux/blob/dev-5.10/Documentation/admin-guide/LSM/apparmor.rst
>> )
>>
>> CONFIG_SECURITYFS=y
>> CONFIG_SECURITY_NETWORK=y
>> CONFIG_SECURITY_PATH=y
>> CONFIG_SECURITY_APPARMOR=y
>> CONFIG_DEFAULT_SECURITY="apparmor"
>> CONFIG_SECURITY_APPARMOR_BOOTPARAM_VALUE=1
>> CONFIG_AUDIT=y
>>
>>
>> In the build tree, kernel is not picking the above config parameters and
>> I was getting the following logs in the config_build_log which suggest that
>> kernel doesn't like these config.
>>
>> tmp/work-shared/hgx/kernel-source/.kernel-meta/cfg/merge_config_build.log
>>
>> Value requested for CONFIG_SECURITY_PATH not in final .config
>> Requested value:  CONFIG_SECURITY_PATH=y
>> CONFIG_SECURITY_PATH=y
>> Actual value:
>>
>> Value requested for CONFIG_SECURITY_APPARMOR not in final .config
>> Requested value:  CONFIG_SECURITY_APPARMOR=y
>> CONFIG_SECURITY_APPARMOR=y
>> Actual value:
>>
>> Value requested for CONFIG_DEFAULT_SECURITY not in final .config
>> Requested value:  CONFIG_DEFAULT_SECURITY="apparmor"
>> CONFIG_DEFAULT_SECURITY="apparmor"
>> Actual value:
>>
>> Value requested for CONFIG_SECURITY_APPARMOR_BOOTPARAM_VALUE not in final
>> .config
>> Requested value:  CONFIG_SECURITY_APPARMOR_BOOTPARAM_VALUE=1
>> CONFIG_SECURITY_APPARMOR_BOOTPARAM_VALUE=1
>> Actual value:
>>
>> Can somebody suggest me what I am missing here?
>>
>> Ratan Gupta
>>
>

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

  reply	other threads:[~2021-08-05  2:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-27  6:12 apparmor support Ratan Gupta
2021-07-27  7:57 ` Ratan Gupta
2021-08-05  2:56   ` Ratan Gupta [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-07-27  6:11 Ratan Gupta

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='CAMhqiMr+b_=bJ=JwuSZUa8eooYVfcEoM7crAgKNH9v6cb2PWOw@mail.gmail.com' \
    --to=ratankgupta31@gmail.com \
    --cc=openbmc@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).