From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: "Sriram, Kannan" <ksriram@ti.com>
Cc: Lorenzo Hern?ndez Garc?a-Hierro <lorenzo@gnu.org>,
SELinux Mail List <selinux@tycho.nsa.gov>
Subject: Re: SELinux for embedded devices...
Date: Fri, 29 Jul 2005 09:44:19 +0100 [thread overview]
Message-ID: <20050729084419.GD11752@lkcl.net> (raw)
In-Reply-To: <45F366B1BC4F7C4A895F0F34C41E61A55113E1@dbde01.ent.ti.com>
On Fri, Jul 29, 2005 at 10:17:18AM +0530, Sriram, Kannan wrote:
> Does SELinux require a writeable filesystem always?
no, it doesn't.
however, nobody with the skills to add xattrs to any of
the read-only filesystems has yet gone ahead and done it /
had a requirement strong enough to justify adding xattrs.
[i added xattrs to tmpfs because i really needed it and there
were enough simple examples to copy].
i too would like to use selinux-enabled squashfs or other
read-only filesystem, because that's a _fantastic_ way of
getting a secure OS. someone's root-kitted the machine?
oh dearie me: reboot it and you _know_ that the squashfs-based
live boot CD will get you back up-and-running.
yep.
throw some money my way and i'll do it for you.
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.
next prev parent reply other threads:[~2005-07-29 8:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-29 4:47 SELinux for embedded devices Sriram, Kannan
2005-07-29 6:09 ` Lorenzo Hernández García-Hierro
2005-07-29 8:44 ` Luke Kenneth Casson Leighton [this message]
2005-07-29 13:16 ` Stephen Smalley
2005-07-29 21:08 ` Christopher J. PeBenito
-- strict thread matches above, loose matches on Subject: below --
2005-07-29 6:30 Sriram, Kannan
2005-07-29 2:20 Sriram, Kannan
2005-07-29 4:12 ` Lorenzo Hernández García-Hierro
2005-07-29 8:55 ` Luke Kenneth Casson Leighton
2005-07-29 13:10 ` 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=20050729084419.GD11752@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.