From: Sander Nagtegaal <trunks-carracho@planet.nl>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Security house-cleaning
Date: Thu, 17 Jun 2004 19:03:21 +0200 [thread overview]
Message-ID: <200406171903.21342.trunks-carracho@planet.nl> (raw)
In-Reply-To: <20040617163740.GB20148@sentinelchicken.org>
*nothing to do with security*
On thing wich would also be a good thing to add ( I'm not sure QEMU has it ) ,
is drag and drop from the guest OS to the emulator. If anyone of you are
familiair with virtual PC then you'll know what I'll mean.
Op donderdag 17 juni 2004 6:37 pm, schreef Tim:
> > One of the main pros of Qemu (among the others) it that it has been
> > designed NOT to run SUID.
> > The only piece of code that need root access is tuntap networking.
> > This problem can be circunvented by:
> > - using sudo for tuntap
> > - using user net (a.k.a slirp)
> > - using vde.
>
> Other future considerations:
> - PCI Proxy support (if it is ever offically supported)
> How will the host OS allow access by QEMU guest in this case?
> - Other bus (USB, firewire, etc) direct access to real hardware
>
>
> Not trying to be alarmist. Just being conservative with code
> quality/security.
>
> tim
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
next prev parent reply other threads:[~2004-06-17 17:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-17 4:38 [Qemu-devel] [PATCH] Security house-cleaning Tim
2004-06-17 15:07 ` Gianni Tedesco
2004-06-17 15:14 ` Renzo Davoli
2004-06-17 15:24 ` Panagiotis Issaris
2004-06-17 15:27 ` Sebastien Bechet
2004-06-17 16:37 ` Tim
2004-06-17 17:03 ` Sander Nagtegaal [this message]
2004-06-17 17:16 ` Gianni Tedesco
2004-06-17 19:59 ` Renzo Davoli
2004-06-17 16:05 ` Tim
2004-06-17 17:41 ` Gianni Tedesco
2004-06-18 4:13 ` Tim
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=200406171903.21342.trunks-carracho@planet.nl \
--to=trunks-carracho@planet.nl \
--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.