Add "Security Process" information to the main website
PATCH 1/1 Add "Security Process" information to the main website
One reporter of a security issue recently complained that it might not be the best idea to store our "Security Process" in the Wiki. Well, while the page in the Wiki is protected (so that only some few people can edit it), it is still possible that someone might find a bug in the Wiki software to alter the page contents...
Anyway, it looks more trustworthy if we present the "Security Process" information in the static website instead. Thus this patch adds the information from the wiki to the Jekyll-based website now.
--- contribute.md | 3 +- contribute/report-a-bug.md | 7 +- contribute/security-process.md | 130 +++++++++++++++++++++++++++++++++ 3 files changed, 135 insertions(+), 5 deletions(-) create mode 100644 contribute/security-process.md
contribute.md +2 -1
@@ -3,7 +3,8 @@ title: Contribute to QEMU! permalink: /contribute/ --- -* Report a bug: [https://bugs.launchpad.net/qemu/](https://bugs.launchpad.net/qemu/)<br>[How to report a bug](report-a-bug/) +* Report a bug in our bugtracker: [https://bugs.launchpad.net/qemu/](https://bugs.launchpad.net/qemu/)<br> + See also [How to report a bug](report-a-bug/) or [How to report a security bug](security-process/) * Clone ([or browse](https://git.qemu.org/?p=qemu.git)) the git repository: <br>`git clone https://git.qemu.org/git/qemu.git`
contribute/report-a-bug.md +3 -4
@@ -17,10 +17,9 @@ When submitting a bug report, please try to do the following: * Do not contribute patches on the bug tracker; send patches to the mailing list. Follow QEMU's [guidelines about submitting patches](https://wiki.qemu.org/Contribute/SubmitAPatch). -Do NOT report security issues (or other bugs, too) as -"private" bugs in the bug tracker. QEMU has a [security -process](https://wiki.qemu.org/SecurityProcess) for issues that should -be reported in a non-public way instead. +Do NOT report security issues (or other bugs, too) as "private" bugs in the +bug tracker. QEMU has a [security process](../security-process) for issues +that should be reported in a non-public way instead. For problems with KVM in the kernel, use the kernel bug tracker instead; the [KVM wiki](https://www.linux-kvm.org/page/Bugs) has the details.
contribute/security-process.md new file +130 -0
130 lines not on this page · raw message
Signature · 1 line
2.18.1
Quoted 3 lines · Thomas Huth
Anyway, it looks more trustworthy if we present the "Security Process" information in the static website instead. Thus this patch adds the information from the wiki to the Jekyll-based website now.
Fair enough; here are some edits so that we can improve the text a bit in the meanwhile.
Quoted 1 line
+We use a GNU Privacy Guard (GnuPG or GPG) keys to secure communications. Mail
Remove "a".
contribute/security-process.md line 34
Quoted 3 lines
contribute/security-process.md new file +3
-0+sent to members of the list can be encrypted with public keys of all members +of the list. We expect to change some of the keys we use from time to time. +Should we change the key, the previous keys will be revoked.
Should a key change, the previous one will be revoked.
contribute/security-process.md line 92
Quoted 2 lines
contribute/security-process.md new file +2
-0+* Is QEMU used in conjunction with a hypervisor (as opposed to TCG binary + translation TCG)?
Two "TCG"s.
contribute/security-process.md line 99
Quoted 4 lines
contribute/security-process.md new file +4
-0+Whenever some or all of these questions have negative answers, what appears to +be a genuine security flaw might be considered of low severity because it could +only be exercised in use cases where QEMU and everything interacting with it is +trusted.
s/genuine/major/
contribute/security-process.md line 109
Quoted 4 lines
contribute/security-process.md new file +4
-0+Prima facie, this bug appears to be a genuine security flaw, with potentially +severe implications. But digging further down, it shows that there are only +two ways to use SD Host Controller emulation, one is via 'sdhci-pci' interface +and the other is via 'generic-sdhci' interface.
I can understand some Latin, but perhaps s/Prima facie/On the surface/
Also, s/it shows that//
Quoted 1 line
+Of these two, the 'sdhci-pci' interface is relatively new and had actually been
s/is relatively new and//
Thanks,
Paolo