From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
qemu-devel@nongnu.org, "Stefano Garzarella" <sgarzare@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v3 1/2] docs: add Secure Coding Practices to developer docs
Date: Thu, 9 May 2019 13:22:08 +0100 [thread overview]
Message-ID: <20190509122208.GP31299@redhat.com> (raw)
In-Reply-To: <20190509121820.16294-2-stefanha@redhat.com>
On Thu, May 09, 2019 at 01:18:19PM +0100, Stefan Hajnoczi wrote:
> At KVM Forum 2018 I gave a presentation on security in QEMU:
> https://www.youtube.com/watch?v=YAdRf_hwxU8 (video)
> https://vmsplice.net/~stefan/stefanha-kvm-forum-2018.pdf (slides)
>
> This patch adds a guide to secure coding practices. This document
> covers things that developers should know about security in QEMU. It is
> just a starting point that we can expand on later. I hope it will be
> useful as a resource for new contributors and will save code reviewers
> from explaining the same concepts many times.
>
> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
> Acked-by: Stefano Garzarella <sgarzare@redhat.com>
> Reviewed-by: Alex Bennée <alex.bennee@linaro.org>
> Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
> ---
> docs/devel/index.rst | 1 +
> docs/devel/secure-coding-practices.rst | 106 +++++++++++++++++++++++++
> 2 files changed, 107 insertions(+)
> create mode 100644 docs/devel/secure-coding-practices.rst
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2019-05-09 12:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-09 12:18 [Qemu-devel] [PATCH v3 0/2] security.rst: add Security Guide to developer docs Stefan Hajnoczi
2019-05-09 12:18 ` [Qemu-devel] [PATCH v3 1/2] docs: add Secure Coding Practices " Stefan Hajnoczi
2019-05-09 12:22 ` Daniel P. Berrangé [this message]
2019-05-10 1:11 ` Li Qiang
2019-05-09 12:18 ` [Qemu-devel] [PATCH v3 2/2] docs: add Security chapter to the documentation Stefan Hajnoczi
2019-05-09 12:21 ` Daniel P. Berrangé
2019-05-10 1:19 ` Li Qiang
2019-05-10 9:54 ` [Qemu-devel] [PATCH v3 0/2] security.rst: add Security Guide to developer docs Stefan Hajnoczi
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=20190509122208.GP31299@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sgarzare@redhat.com \
--cc=stefanha@redhat.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 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.