All of lore.kernel.org
 help / color / mirror / Atom feed
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: Tue, 27 Apr 2004 13:14:12 +0100	[thread overview]
Message-ID: <20040427121412.GC741@vnl.com> (raw)
In-Reply-To: <20040422035659.GQ731@peach.ece.utexas.edu>

On Wed, Apr 21, 2004 at 10:56:59PM -0500, Tom Brown wrote:
> Not specifically. SEU's are more likely in space but they do occur in
> terrestrial systems. I believe SEU's can be encouraged by a solar
> radiation storm or simple heat[1]. We want to see at what rate they
> might create security problems.

Yes, and like random decays from the material in ceramic
pack IC's if I remember correctly. Interesting idea. 

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

  reply	other threads:[~2004-04-27 12:14 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
2004-04-22  3:56       ` Tom Brown
2004-04-27 12:14         ` Dale Amon [this message]
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=20040427121412.GC741@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.