From: "Lamont R. Peterson" <lrp@xmission.com>
To: CNGUYEN <CNguyen@mykotronx.com>,
"'Russell Coker'" <russell@coker.com.au>,
"'Stephen D. Smalley'" <sds@epoch.ncsc.mil>,
"'selinux@tycho.nsa.gov'" <selinux@tycho.nsa.gov>
Subject: Re: Making OPIE/QTOPIA aware of SELinux
Date: Fri, 21 Feb 2003 07:57:56 -0700 [thread overview]
Message-ID: <200302210757.56785.lrp@xmission.com> (raw)
In-Reply-To: <FD2221F5E1A8184DB61AFCE064C395F1C91CEF@torexch1.mykotronx.com>
On Thursday 20 February 2003 12:42 pm, CNGUYEN wrote:
> Applications <----
> ---- |
> OPIE/QTOPIA <---------|
> --- |
> SELinux |
> --- |
> Device Drivers <-------|
If I understand the architecture of the kernel (and particularly, how SELinux
affects the kernel) then I would have to say that your diagram is incorrect.
SELinux does not sit on top of the kernel; it "IS" the kernel.
Qtopia (I don't know OPIE) does not bypass the kernel in order to talk to
devices directly. There is nothing (other than compiling SELinux into your
"embedded" kernel) that needs be done for Qtopia to run securely.
However, if I were to do this, I would write some Qtopia apps to wrap around
SELinux specific tools such as spasswd, and would explore the "login"
facility that Qtopia Desktop uses to communicate with Qtopia devices.
--
Sincerely,
Lamont R. Peterson <lrp@xmission.com>
--
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-02-21 14:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-20 19:42 Making OPIE/QTOPIA aware of SELinux CNGUYEN
2003-02-21 9:33 ` Tom
2003-02-21 14:57 ` Lamont R. Peterson [this message]
2003-02-21 15:13 ` Russell Coker
-- strict thread matches above, loose matches on Subject: below --
2003-02-21 15:05 CNGUYEN
2003-02-20 16:42 CNGUYEN
2003-02-20 19:36 ` Russell Coker
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=200302210757.56785.lrp@xmission.com \
--to=lrp@xmission.com \
--cc=CNguyen@mykotronx.com \
--cc=russell@coker.com.au \
--cc=sds@epoch.ncsc.mil \
--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.