From: Magnus Damm <damm@opensource.se>
To: pg@futureware.at, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] building a virus-proof PC with Qemu
Date: Tue, 23 Nov 2004 15:38:12 +0100 [thread overview]
Message-ID: <1101220692.8464.37.camel@localhost> (raw)
In-Reply-To: <200411231441.34327.mailinglists@futureware.at>
On Tue, 2004-11-23 at 14:41, Philipp Gühring wrote:
> Am Dienstag, 23. November 2004 13:46 schrieb Andreu Escudero:
> > Seems absurd to me...
> > Haw will you now if a byte comes from a "trusted source"?
>
> I can´t say for sure, whether a byte comes from a trusted source.
> But I have a way so say for sure where an evil byte comes from.
So, you mean that each input device in the system emulator could be
marked as trusted or untrusted, and the data from untrusted input
sources is kept track of. Any calculations that use untrusted in-data
results in untrusted out-data. But then what do we do with the all the
untrusted data? Refuse to store it? Or just limit the network bandwidth
for untrusted data to cope with worms?
/ magnus
next prev parent reply other threads:[~2004-11-23 14:49 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
2004-11-23 13:41 ` Philipp Gühring
2004-11-23 14:38 ` Magnus Damm [this message]
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=1101220692.8464.37.camel@localhost \
--to=damm@opensource.se \
--cc=pg@futureware.at \
--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).