From: ramsdell@mitre.org (John D. Ramsdell)
To: Karl MacMillan <kmacmillan@tresys.com>
Cc: "Joshua D. Guttman disp: current" <guttman@mitre.org>,
SE Linux <selinux@tycho.nsa.gov>
Subject: Re: Information flow models
Date: 11 Dec 2003 08:10:32 -0500 [thread overview]
Message-ID: <ogtr7zbebzr.fsf@divan.mitre.org> (raw)
In-Reply-To: <1071087506.6729.175.camel@colossus.columbia.tresys.com>
Karl MacMillan <kmacmillan@tresys.com> writes:
> The arrows are directed edges (arcs if you prefer). They mean that
> there was 1 or more allow rules that defined an information flow
> between the nodes.
and from a previous note:
> Obviously the "<-" represents an edge. If you follow the edges it
> appears there is a flow between a_t and c_t when in fact there isn't.
> The new version would generate a graph that looks like this:
>
> [a_t]<-[b_t:blk_file] [b_t:tcp_socket]<-[c_t]
You documentation states that flows occur between types, but your
graph has type class pairs as nodes, sometimes as a source and
sometimes as a destination. What does it mean for information to
originate from b_t:blk_file? What does it mean for information to get
to b_t:tcp_socket?
John
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2003-12-11 13:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-05 14:57 Problems loading policy Stephen
2003-12-05 18:36 ` Dale Amon
2003-12-05 20:32 ` Information flow models John D. Ramsdell
2003-12-08 17:57 ` Karl MacMillan
2003-12-10 13:18 ` John D. Ramsdell
2003-12-10 15:11 ` Karl MacMillan
2003-12-10 15:29 ` John D. Ramsdell
2003-12-10 15:37 ` Karl MacMillan
2003-12-10 19:06 ` Joshua D. Guttman
2003-12-10 20:18 ` Karl MacMillan
2003-12-11 13:10 ` John D. Ramsdell [this message]
2003-12-11 16:04 ` Karl MacMillan
2003-12-11 17:43 ` Joshua D. Guttman
2003-12-11 20:23 ` Stephen Smalley
2003-12-11 20:45 ` Stephen Smalley
2003-12-11 20:46 ` Karl MacMillan
2003-12-11 21:00 ` Stephen Smalley
2003-12-23 19:12 ` Trent Jaeger
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=ogtr7zbebzr.fsf@divan.mitre.org \
--to=ramsdell@mitre.org \
--cc=guttman@mitre.org \
--cc=kmacmillan@tresys.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.