From: Dale Amon <amon@vnl.com>
To: Tom Brown <tdbrown@uiuc.edu>
Cc: Ed Street <edstreet@street-tek.com>,
SELinux@tycho.nsa.gov, "'Michael Ihde'" <ihde@uiuc.edu>
Subject: Re: SELinux security in the face of single bit errors
Date: Sat, 17 Apr 2004 12:22:13 +0100 [thread overview]
Message-ID: <20040417112213.GE21171@vnl.com> (raw)
In-Reply-To: <20040416184516.GV4773@peach.ece.utexas.edu>
On Fri, Apr 16, 2004 at 01:45:16PM -0500, Tom Brown wrote:
> We are most interested in how single-bit errors affect security software
> in general, rather than the protection of some specific software. If
> we continue the project beyond this semester (likely if initial results
> offer some hope) we may branch out to look at more than basic SELinux.
Just curious. Is this a study of the effect of SEU's
in spacecraft hardware?
--
------------------------------------------------------
Dale Amon amon@islandone.org +44-7802-188325
International linux systems consultancy
Hardware & software system design, security
and networking, systems programming and Admin
"Have Laptop, Will Travel"
------------------------------------------------------
--
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:[~2004-04-17 11:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-15 23:16 SELinux security in the face of single bit errors tdbrown
2004-04-16 12:44 ` Ed Street
2004-04-16 18:45 ` Tom Brown
2004-04-17 11:22 ` Dale Amon [this message]
2004-04-22 3:56 ` Tom Brown
2004-04-27 12:14 ` Dale Amon
2004-04-17 19:19 ` Ed Street
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=20040417112213.GE21171@vnl.com \
--to=amon@vnl.com \
--cc=SELinux@tycho.nsa.gov \
--cc=edstreet@street-tek.com \
--cc=ihde@uiuc.edu \
--cc=tdbrown@uiuc.edu \
/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.