From: Anthony Liguori <anthony@codemonkey.ws>
To: Alexander Graf <agraf@suse.de>
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>,
Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>,
Bique Alexandre <bique.alexandre@gmail.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/7] ATAPI CDROM passthrough v5
Date: Mon, 18 Oct 2010 19:10:31 -0500 [thread overview]
Message-ID: <4CBCE1F7.5000304@codemonkey.ws> (raw)
In-Reply-To: <DB3D4335-B29E-403F-9670-C82D5133EE52@suse.de>
On 10/18/2010 06:29 PM, Alexander Graf wrote:
>> A user will get a really nasty surprise if they think they can use a flag or rely on QEMU to prevent a VM from doing something nasty with a device. If they have this feeling of security, they're likely to chmod the device to allow unprivileged users to access it.
>>
>> But how a device handles ATAPI commands is totally up to the device. If you issue the wrong sequence, I'm sure there are devices out there that totally hose themselves. Are you absolutely confident that every ATAPI device out there is completely safe against hostile code provided that you simply prevent the FW update commands? I'm certainly not.
>>
> Ping?
>
Who are you pinging?
Regards,
Anthony Liguori
> Alex
>
>
>
next prev parent reply other threads:[~2010-10-19 0:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-12 17:18 [Qemu-devel] [PATCH 0/7] ATAPI CDROM passthrough v5 Ian Jackson
2009-08-12 17:26 ` [Qemu-devel] " Ian Jackson
2009-08-12 22:00 ` [Qemu-devel] " Christoph Hellwig
2009-08-13 16:44 ` Ian Jackson
2009-08-24 13:18 ` Anthony Liguori
2009-08-28 20:21 ` Bique Alexandre
2009-08-29 19:35 ` Carl-Daniel Hailfinger
2009-08-29 20:49 ` Anthony Liguori
2009-08-29 21:10 ` Carl-Daniel Hailfinger
2009-08-30 0:14 ` Anthony Liguori
2010-10-18 23:29 ` Alexander Graf
2010-10-19 0:10 ` Anthony Liguori [this message]
2010-10-19 6:17 ` Alexander Graf
2010-10-19 14:27 ` Michal Suchanek
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=4CBCE1F7.5000304@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=Ian.Jackson@eu.citrix.com \
--cc=agraf@suse.de \
--cc=bique.alexandre@gmail.com \
--cc=c-d.hailfinger.devel.2006@gmx.net \
--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).