From: Leesoo Ahn <lsahn@wewakecorp.com>
To: Casey Schaufler <casey@schaufler-ca.com>
Cc: linux-security-module@vger.kernel.org
Subject: Re: [LSM Stacking] SELinux policy inside container affects aprocessonHost
Date: Tue, 25 Jul 2023 12:16:41 +0900 [thread overview]
Message-ID: <57747ff8-7433-9a76-0e76-c0c292acfd26@wewakecorp.com> (raw)
In-Reply-To: <7ef141bc-8a02-4ef0-c970-8de3e0146139@schaufler-ca.com>
2023-07-25 오전 6:35에 Casey Schaufler 이(가) 쓴 글:
> On 7/23/2023 7:29 PM, Leesoo Ahn wrote:
> > 2023-07-18 오전 12:51에 Casey Schaufler 이(가) 쓴 글:
> >> On 7/17/2023 8:24 AM, Leesoo Ahn wrote:
> >> > 23. 7. 7. 23:20에 Paul Moore 이(가) 쓴 글:
> >> >> On Fri, Jul 7, 2023 at 4:29 AM Leesoo Ahn <lsahn@wewakecorp.com>
> >> wrote:
> >> >> > 2023-07-06 오후 10:43에 Paul Moore 이(가) 쓴 글:
> > [...]> >> If you are interested in stacking SELinux and AppArmor, I
> > believe the
> >> >> only practical solution is to run SELinux on the host system
> >> (initial
> >> >> namespace) and run AppArmor in the containers. Even in a world where
> >> >> SELinux is fully namespaced, it would likely still be necessary
> >> to run
> >> >> some type of SELinux policy on the host (initial namespace) in order
> >> >> to support SELinux policies in the containers.
> >> >
> >> > Thank you for the reply. It really helped me to know the current
> >> > status of them and what to do now.
> >> >
> >> > Just a little information for who is interested in the stacking that
> >> > we decided to branch the LSM hooks by which lsm the current
> >> process is
> >> > in instead of entirely calling them in order.
> >>
> >> Could you describe your approach more fully?
> >
> > As far as I know, the current stacking feature is implemented calling
> > the entire hooks in order of 'lsm=' boot parameter. But our desire
> > must be calling a proper hook at a time by a task's current LSM, for
> > instance Apparmor 'or' SELinux instead of 'and'.
>
> SELinux and Smack rely on the fact that they manage security attributes
> on all subjects and all objects. On a system where some objects are not
> labeled because they are being managed by AppArmor instead, you are
> going to have a security state that is muddled. How would you have a
> host system that uses SELinux handle files in a container that is using
> only AppArmor?
I think we could deal with that using origin call_ macro only if the
following cases that alloc a task, socket, make a file and so forth
which do newing objects and subjects that must have both security
context for preventing a security state that would be muddled. On the
other hands, in a case of operations that like read, load, mmap are to
call the customized call_ macro with ilsm to conditionally branch.
[...]
> I would rather see a local copy of the hook lists for processes that
> use a different set than the base system.
Could you explain the latter one, please?
best regards,
Leesoo
next prev parent reply other threads:[~2023-07-25 3:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-06 5:12 [LSM Stacking] SELinux policy inside container affects a process on Host Leesoo Ahn
2023-07-06 13:43 ` Paul Moore
2023-07-07 0:35 ` Serge E. Hallyn
2023-07-07 1:17 ` [LSM Stacking] SELinux policy inside container affects a processon Host Leesoo Ahn
2023-07-07 8:28 ` [LSM Stacking] SELinux policy inside container affects a process on Host Leesoo Ahn
2023-07-07 14:20 ` Paul Moore
2023-07-07 16:50 ` Casey Schaufler
2023-07-07 21:41 ` Paul Moore
2023-07-18 10:34 ` Dr. Greg
2023-07-18 17:20 ` Casey Schaufler
2023-07-19 18:45 ` Dr. Greg
2023-07-20 0:21 ` Casey Schaufler
2023-07-21 23:55 ` Dr. Greg
2023-07-17 15:24 ` [LSM Stacking] SELinux policy inside container affects a processon Host Leesoo Ahn
2023-07-17 15:51 ` Casey Schaufler
2023-07-24 2:29 ` [LSM Stacking] SELinux policy inside container affects aprocesson Host Leesoo Ahn
2023-07-24 21:35 ` Casey Schaufler
2023-07-25 3:16 ` Leesoo Ahn [this message]
2023-07-28 1:54 ` [LSM Stacking] SELinux policy inside container affects a processon Host Leesoo Ahn
2023-08-06 17:16 ` Dr. Greg
2023-08-06 19:25 ` Paul Moore
2023-08-08 6:40 ` Dr. Greg
2023-08-08 14:32 ` Paul Moore
2023-07-07 17:51 ` [LSM Stacking] SELinux policy inside container affects a process on Host Dr. Greg
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=57747ff8-7433-9a76-0e76-c0c292acfd26@wewakecorp.com \
--to=lsahn@wewakecorp.com \
--cc=casey@schaufler-ca.com \
--cc=linux-security-module@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.