From: Tom <tom@lemuria.org>
To: Will Dye <willdye@dsndata.com>
Cc: Bede McCall <bede@mitre.org>, selinux@tycho.nsa.gov
Subject: Re: SELinux as a desktop / workstation?
Date: Sun, 13 May 2001 03:03:48 +0200 [thread overview]
Message-ID: <20010513030347.C9636@lemuria.org> (raw)
In-Reply-To: <m14ygd1-000098C@zuul.dsndata.com>; from willdye@dsndata.com on Sat, May 12, 2001 at 04:08:42PM -0500
On Sat, May 12, 2001 at 04:08:42PM -0500, Will Dye wrote:
> Extending the idea further, what if we had very smart clients,
> but processing (that is of interest to the server) may only run
> on a *virtual* machine. The virtual machine mostly runs on the
> local client, but the integrity of the VM is cryptographically
> authenticated by the server before its output is approved. In
> this scenario, the "dumb client" is a virtual machine, which
> runs on any of a variety of platforms -- even an ordinary PC
> somewhere on the Internet.
a simple form of this is done in almost all multiplayer online games
(mostly to prevent cheating). the experience there is that it doesn't
work.
> Besides, if you try to improve security by having only a
> restricted class of machines on your network, you eventually
> still have to set up a scheme to prove that the "dumb client"
> at a certain location isn't really Mallory's PC in disguise.
> Thus, it seems like you'll have to make a VM model at some
> point or another anyway, and use that model to try to validate
> that the client hasn't been modified.
I have serious doubts that this will *ever* work. as long as the user
can theoretically access data that he shouldn't, he'll find a way to
actually do it.
the VM part has actually been used a while ago, and was even called
that - VMS. thin clients all over again, in VMS they just processed
user input and server output and ALL actual computations were done on
the server machine.
> The PC can run whatever junk the user wants, including Outlook
> viruses and who-knows-what. Processing that is of interest to
> the server, however, has to run on a VM.
and the VM will be hacked, reverse-engineered and pried wide open.
people do it in order to get better scores at GAMES. I'm fairly
pessimistic at their potential when it's about serious data instead.
a good general security model should - IMHO - work very much like a
good program: don't make assumptions and don't take shortcuts. you
can't assume the VM is what it should be once it left your hands. you
can't assume the line is clear or your crypto layer has not been broken
(the german u-boot command assumed that enigma was unbreakable - it may
have been the deciding factor on the sea theatre).
--
-- http://web.lemuria.org
--
--
You have received this message because you are subscribed to the selinux 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:[~2001-05-13 1:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-08 11:55 SELinux as a desktop / workstation? Jan Petranek
2001-05-08 17:31 ` Will Dye
2001-05-11 21:16 ` g.montgomery
2001-05-12 0:51 ` Bede McCall
2001-05-12 6:16 ` g.montgomery
2001-05-12 21:08 ` Will Dye
2001-05-13 1:03 ` Tom [this message]
2001-05-18 14:22 ` Jan Petranek
2001-05-18 17:58 ` Re[2]: " Maksim Otstavnov
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=20010513030347.C9636@lemuria.org \
--to=tom@lemuria.org \
--cc=bede@mitre.org \
--cc=selinux@tycho.nsa.gov \
--cc=willdye@dsndata.com \
/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.