All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel J Walsh <dwalsh@redhat.com>
To: "Patrick K., ITF" <cto@itechfrontiers.com>, selinux@tycho.nsa.gov
Subject: Re: What do you mean by a 'domain'.
Date: Mon, 07 Apr 2014 07:45:02 -0400	[thread overview]
Message-ID: <53428FBE.3050302@redhat.com> (raw)
In-Reply-To: <53427577.1070704@itechfrontiers.com>


On 04/07/2014 05:52 AM, Patrick K., ITF wrote:
>
> On 4/7/2014 5:24 AM, dE wrote:
>> Hi!
>>
>> Sorry for the trival question; but on reading various SELinux resources,
>> it appears everyone talks about some 'domain' but no one defines what is
>> it.
>>
>> So I wanna what what is a domain in SELinux.
>>
>>
>> Thank you!
>
> Hello,
>
> Generally a domain is a scope or realm, consisting of related contexts
> in which you define and operate your security components (depending on
> your security model) using a combination of:
>
> SELinux  user, role, type and level (optionally, MLS sensitivity level)
>
>
> Particularly, a domain is also used interchangeably with SELinux "type"
>
> In addition, in RBAC (Role-based security model) to some extent a
> "role" can serve as an intermediary between domains (types) and be
> part of it.
>
> Representations:
>
> SELinux User :  SELinux Role :  SELinux Type :  Sensitivity Level
> unconfined_u :  unconfined_r : unconfined_t  : s0-s0:c0.c1024
>
>
> # ps -eZ
> # ls -laZ
>
>
>
>
> Best Regards,
>
>
I would describe a "Domain" as in SELinux type applied to a process as
opposed to a type  applied to an Object like a file, port, interface,
network ...

  reply	other threads:[~2014-04-07 11:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-07  9:24 What do you mean by a 'domain' dE
2014-04-07  9:52 ` Patrick K., ITF
2014-04-07 11:45   ` Daniel J Walsh [this message]
2014-04-07 11:54 ` Stephen Smalley
2014-04-08  5:51   ` dE
2014-04-08  6:43   ` Patrick K., ITF

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=53428FBE.3050302@redhat.com \
    --to=dwalsh@redhat.com \
    --cc=cto@itechfrontiers.com \
    --cc=selinux@tycho.nsa.gov \
    /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.