From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: qemu-devel@nongnu.org, peter.maydell@linaro.org
Subject: Re: [RFC PATCH v2] gitlab: update issue template for binary test cases
Date: Mon, 11 May 2026 18:29:25 +0100 [thread overview]
Message-ID: <agIR9Q5xjjdu4J7R@redhat.com> (raw)
In-Reply-To: <20260511161757.105994-1-alex.bennee@linaro.org>
On Mon, May 11, 2026 at 05:17:57PM +0100, Alex Bennée wrote:
> Binary test cases are sketchy because they can be vectors for phishing
> and other malware. Lets strongly hint that source bases tests are
> preferred and binaries should have their provenance declared.
>
> Suggested-by: Peter Maydell <peter.maydell@linaro.org>
> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
>
> ---
> v2
> - typos
> ---
> .gitlab/issue_templates/bug.md | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/.gitlab/issue_templates/bug.md b/.gitlab/issue_templates/bug.md
> index 53a79f58284..e20f586008d 100644
> --- a/.gitlab/issue_templates/bug.md
> +++ b/.gitlab/issue_templates/bug.md
> @@ -55,6 +55,10 @@ https://www.qemu.org/contribute/security-process/
> <!--
> Attach logs, stack traces, screenshots, etc. Compress the files if necessary.
> If using libvirt, libvirt logs and XML domain information may be relevant.
> +
> +If attaching binary test cases you should describe where they were obtained
> +from, preferably linking to the original source. We greatly prefer test cases in
> +the form of source code that can be audited before compiling by the engineer.
> -->
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
With regards,
Daniel
--
|: https://berrange.com ~~ https://hachyderm.io/@berrange :|
|: https://libvirt.org ~~ https://entangle-photo.org :|
|: https://pixelfed.art/berrange ~~ https://fstop138.berrange.com :|
prev parent reply other threads:[~2026-05-11 17:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-11 16:17 [RFC PATCH v2] gitlab: update issue template for binary test cases Alex Bennée
2026-05-11 17:29 ` Daniel P. Berrangé [this message]
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=agIR9Q5xjjdu4J7R@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=peter.maydell@linaro.org \
--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