All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Lorenzo Hern?ndez Garc?a-Hierro <lorenzo@gnu.org>
Cc: "Sriram, Kannan" <ksriram@ti.com>,
	SELinux Mail List <selinux@tycho.nsa.gov>
Subject: Re: SELinux for embedded devices...
Date: Fri, 29 Jul 2005 09:55:40 +0100	[thread overview]
Message-ID: <20050729085540.GF11752@lkcl.net> (raw)
In-Reply-To: <1122610349.14844.21.camel@localhost.localdomain>

On Fri, Jul 29, 2005 at 06:12:29AM +0200, Lorenzo Hern?ndez Garc?a-Hierro wrote:

> El vie, 29-07-2005 a las 07:50 +0530, Sriram, Kannan escribi?:
> > Hello all,
> > 
> >  I'm a newbie to SELinux, trying to figure out if SELinux is applicable/
> > suitable to embedded system security, especially mobile terminals/
> > smartphones. I have the following very basic questions... Pls help me
> > out, or redirect me to the appropriate forum.
> > 
> > 1. Is SELinux applicable and suitable for mobile equipment, where the
> > end user always has root privileges? Has SELinux been ported to any
> > embedded device yet (some ARM platform??).

> I was working on the design of extended attributes for JFFS2 (in which
> SELinux relies for labeling file-system objects), even got help from an
> Intel guy, but I got stuck at it, without any resources for testing, and
> the Intel guy who was willing to work together with me was requested for
> legal approbation before doing anything. Thus, time passed and I
> couldn't go a step further on doing anything serious about it.

 i have a complete test environment for doing this sort of
 thing, it's been sitting unused for several months because
 the project has been shut down.

 the device is a skyminder - a 90Mhz Cirrus Logic "Maverick"
 ARM 720T and it contains a GSM radio module and a GPS module.
 the company ran out of money to do things like, oh i dunno,
 correct the radio interference from the GSM radio module
 to the audio codec and the microphone for example, which
 was only discovered recently when i developed enough of the
 drivers and test procedures to notice it was a problem.

 ... but _other_ than that, the device is perfectly serviceable,
 runs a 2.6.11 kernel, uses JFFS2 on its 16Mbyte flash RAM,
 i have all the source code blah blah full development
 environment blah blah.

 yes i briefly considered adding selinux in to the mix, but
 not on the budget they were paying me.

 l.


--
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.

  reply	other threads:[~2005-07-29  9:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-29  2:20 SELinux for embedded devices Sriram, Kannan
2005-07-29  4:12 ` Lorenzo Hernández García-Hierro
2005-07-29  8:55   ` Luke Kenneth Casson Leighton [this message]
2005-07-29 13:10 ` Stephen Smalley
  -- strict thread matches above, loose matches on Subject: below --
2005-07-29  4:47 Sriram, Kannan
2005-07-29  6:09 ` Lorenzo Hernández García-Hierro
2005-07-29  8:44 ` Luke Kenneth Casson Leighton
2005-07-29 13:16   ` Stephen Smalley
2005-07-29 21:08     ` Christopher J. PeBenito
2005-07-29  6:30 Sriram, Kannan

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=20050729085540.GF11752@lkcl.net \
    --to=lkcl@lkcl.net \
    --cc=ksriram@ti.com \
    --cc=lorenzo@gnu.org \
    --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.