From: Anthony Liguori <aliguori@us.ibm.com>
To: qemu-devel <qemu-devel@nongnu.org>
Cc: Chris Wright <chrisw@redhat.com>,
Corey Bryant <coreyb@linux.vnet.ibm.com>,
Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>,
Avi Kivity <avi@redhat.com>
Subject: [Qemu-devel] [RFC] QEMU Code Audit Team
Date: Fri, 06 Jan 2012 09:19:45 -0600 [thread overview]
Message-ID: <4F071111.6080306@us.ibm.com> (raw)
Hi,
I had an idea I wanted to share and see what level of interest there was in
participating and if anyone knows of a process that other projects follow for this.
I'd like to start a more formal and transparent security audit of QEMU. The way
I'd imagine it working is something like this:
1) People volunteer to be part of the audit team
2) Two people walk through a particular piece of code and independently flag
anything that looks like a potential security issue.
3) Two people independently review everything that's flagged to see if there's a
security issue.
Step (3) is something that requires a fairly deep understanding of QEMU but step
(2) is probably something that a lot of people could participate in.
I'd want to focus initially on the common PC devices. The list isn't all that
large and a review like this should only take a few hours to complete each step.
Would folks be interested in participating in something like this? If so, I can
start organizing it.
Regards,
Anthony Liguori
next reply other threads:[~2012-01-06 15:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-06 15:19 Anthony Liguori [this message]
2012-01-06 16:01 ` [Qemu-devel] [RFC] QEMU Code Audit Team Stefan Hajnoczi
2012-01-06 16:14 ` Stefan Weil
2012-01-06 16:08 ` Corey Bryant
2012-01-06 17:25 ` Chris Wright
2012-01-08 14:01 ` Dor Laor
2012-01-08 16:54 ` Stefan Hajnoczi
2012-01-06 17:37 ` Chris Wright
2012-01-06 20:02 ` Andreas Färber
2012-01-06 20:42 ` Anthony Liguori
2012-01-07 3:09 ` Peter Maydell
2012-01-07 10:42 ` Stefan Hajnoczi
2012-01-10 12:58 ` Kevin Wolf
2012-01-10 13:22 ` Anthony Liguori
2012-01-10 13:33 ` Kevin Wolf
2012-01-10 13:39 ` Andreas Färber
2012-01-10 14:55 ` Kevin Wolf
2012-01-10 15:41 ` Peter Maydell
2012-01-10 16:31 ` Andreas Färber
2012-01-10 14:21 ` Anthony Liguori
2012-01-10 3:31 ` Zhi Yong Wu
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=4F071111.6080306@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--cc=chrisw@redhat.com \
--cc=coreyb@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.com \
/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).