From: Andreu Escudero <canuda10@gmail.com>
To: Piotras <piotras@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] building a virus-proof PC with Qemu
Date: Tue, 23 Nov 2004 13:46:36 +0100 [thread overview]
Message-ID: <4a1d883204112304461e5bbb27@mail.gmail.com> (raw)
In-Reply-To: <da63183704112304315e4f657@mail.gmail.com>
Seems absurd to me...
Haw will you now if a byte comes from a "trusted source"?
And if you know what is a trusted source and what is not... you don't
need anything like extrange imformation propagation...
On Tue, 23 Nov 2004 13:31:59 +0100, Piotras <piotras@gmail.com> wrote:
> Hi!
>
> Imagine that with every byte stored on disk image, the emulated
> memory and CPU registers we associate a flag indicating if the
> byte come from "trusted" source. This information would propagate
> with every memory/disk access (data-flow tracking).
>
> Before Qemu would translate a block of code the trusted bits could
> be checked to see if the code is "trusted". Of course there are
> issues with dynamic loaders, dynamic compilers, etc. And it's not
> going to work well with scripted code.
>
> Possible usage:
> * building virus-proof PC,
> * automate hunting for worms/exploits on Internet.
>
> Opinions?
>
> Piotrek
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
>
--
Das Experimental Kunstwerk
next prev parent reply other threads:[~2004-11-23 12:56 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
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 [this message]
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=4a1d883204112304461e5bbb27@mail.gmail.com \
--to=canuda10@gmail.com \
--cc=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 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.