qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Piotras <piotras@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] building a virus-proof PC with Qemu
Date: Tue, 23 Nov 2004 18:37:41 +0100	[thread overview]
Message-ID: <da63183704112309374be23309@mail.gmail.com> (raw)
In-Reply-To: <1101221775.8460.44.camel@localhost>

Hi!

In fact I thought about the idea in context of military/classified
environment. However the technology could be interesting to 
large corporations as well. Especially that Qemu performance 
may justify this in not-so-distant future.

The technology could be transparent to the operating system 
(build into qemu-softmmu). I don't see why this shouldn't work 
with Windows. The "trusted" flag is not visible for the guest 
(it's stored in "hidden" part of qemu disk image, "hidden" 
registers, and "hidden" RAM area). The flag could be handled 
transparently by Qemu, except that when trying to execute 
"untrusted" code it could just generate illegal opcode exception.

The extension to the original idea could be to trace sensitive 
(classified) data to for example block all ethernet frames that 
may contain sensitive data from leaving the system.

How to mark data as "trusted"? There are many possibilities. 
For example when inserting CD-ROM we could have a checkbox
(handled by host) to mark all data read from CD-ROM as 
"trusted". Another possibility is to have a special utility running 
inside the guest that could tell Qemu that a given file (set of 
bytes on disk) contains classified data.


Regards,

Piotrek

On Tue, 23 Nov 2004 15:56:15 +0100, Magnus Damm <damm@opensource.se> wrote:
> Hello again,
> 
> On Tue, 2004-11-23 at 13:44, Bochnig, Martin wrote:
> > Hi,
> >
> > most of you know that: The easiest and most secure (100.00%) option
> > imaginable is to boot from cd/dvd and to keep the registry (in case of
> > m$-win) - or other files requiring write access - inside of a ramdrive.
> > Works.
> 
> I think the idea is really nice, tried to convince some people employed
> by the Swedish army about this two years ago. The Swedish army is very
> picky about classified data and if a computer ever gets near classified
> information the machine has to be marked as classified and then the
> entire machine has to be handled very strictly. Booting from cdrom is
> simple and effective.
> 
> Do you have any pointers how to do this with Windows (2k/XP) ?
> 
> Thanks!
> 
> / magnus

  parent reply	other threads:[~2004-11-23 17:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-23 12:31 [Qemu-devel] building a virus-proof PC with Qemu Piotras
2004-11-23 12:44 ` Bochnig, Martin
2004-11-23 14:00   ` Magnus Damm
2004-11-23 14:56   ` Magnus Damm
2004-11-23 15:19     ` Paul Brook
2004-11-23 17:37     ` Piotras [this message]
2004-11-23 21:20       ` Bochnig, Martin
2004-11-23 22:41         ` Karl Magdsick
2004-11-23 23:33           ` Magnus Damm
2004-11-23 12:46 ` Andreu Escudero
2004-11-23 13:41   ` Philipp Gühring
2004-11-23 14:38     ` Magnus Damm
2004-11-23 12:54 ` Paul Brook

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=da63183704112309374be23309@mail.gmail.com \
    --to=piotras@gmail.com \
    --cc=qemu-devel@nongnu.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).