From: Joshua Brindle <brindle@quarksecurity.com>
To: Kernel freak <kernelfreak@gmail.com>
Cc: "selinux@tycho.nsa.gov" <SELinux@tycho.nsa.gov>
Subject: Re: What is Type Enforcement Model in SELinux?
Date: Sat, 01 Mar 2014 09:01:57 -0500 [thread overview]
Message-ID: <5311E855.1070608@quarksecurity.com> (raw)
In-Reply-To: <CAOFt0CQYn+Sku39NOHn4ggX1_8O3y6uvZLtfS1_TQJhirANfNQ@mail.gmail.com>
Kernel freak wrote:
> Hello Friends,
> I am writing a report and I need to write about TE
> model in SELinux. I searched around the net, but all the articles I read
> beat around the bush and never say like ok, this is TE model for SELinux.
> Can anyone be so kind and please point me out to some links which say
> about TE model in SELinux and if possible an appropriate model. Thank
> you for your time and patience.
>
You are probably having problems finding a succinct description of the
model because, to my knowledge, there is no complete description as it
exists today.
I'm sure Stephen will have other suggestions but you can start with the
old Flask papers:
http://www.cs.utah.edu/flux/fluke/html/flask.html
The type enforcement access matrix model hasn't much changed since then
but various things related to what that means on a system have (such as
constraints, network access control, named transitions) evolved over time.
next prev parent reply other threads:[~2014-03-01 14:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-01 11:23 What is Type Enforcement Model in SELinux? Kernel freak
2014-03-01 13:14 ` Bryan Harris
2014-03-01 13:26 ` Kernel freak
2014-03-01 13:58 ` Brandon Whalen
2014-03-01 14:01 ` Joshua Brindle [this message]
2014-03-01 14:08 ` Kernel freak
2014-03-01 17:13 ` Kernel freak
2014-03-03 12:51 ` Stephen Smalley
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=5311E855.1070608@quarksecurity.com \
--to=brindle@quarksecurity.com \
--cc=SELinux@tycho.nsa.gov \
--cc=kernelfreak@gmail.com \
/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.