From: "Alex Bennée" <alex.bennee@linaro.org>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
Pierrick Bouvier <pierrick.bouvier@oss.qualcomm.com>,
Thomas Huth <thuth@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Mauro Matteo Cascella <mcascell@redhat.com>
Subject: Re: [qemu-web PATCH v2 3/3] contribute: switch security process to gitlab confidential issues
Date: Thu, 18 Jun 2026 14:42:43 +0100 [thread overview]
Message-ID: <87qzm4ezho.fsf@draig.linaro.org> (raw)
In-Reply-To: <20260618132058.1044341-4-berrange@redhat.com> ("Daniel P. Berrangé"'s message of "Thu, 18 Jun 2026 14:20:58 +0100")
Daniel P. Berrangé <berrange@redhat.com> writes:
> It is no longer viable to handle the incredible volumes of
> AI assisted security disclosures via email, nor are extended
> embargos practical or useful.
>
> Remove all information about the current security process and
> instruct reporters to use 'confidential' issues. In contrast
> to the old highly restrictive "need to know" approach, the
> new approach makes all security issues visible to all QEMU
> maintainers immediately.
>
> The focus is on making issues public as soon as possible with
> a viable patch. Co-ordinated disclosure will no longer be
> attempted and nor will requests to embargoes be accepted.
>
> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
Reviewed-by: Alex Bennée <alex.bennee@linaro.org>
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
next prev parent reply other threads:[~2026-06-18 13:42 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-18 13:20 [qemu-web PATCH v2 0/3] switch to GitLab confidential issues for security disclosure Daniel P. Berrangé
2026-06-18 13:20 ` [qemu-web PATCH v2 1/3] contribute: reformat/restructure bug report guidance Daniel P. Berrangé
2026-06-18 13:40 ` Alex Bennée
2026-06-18 13:55 ` Philippe Mathieu-Daudé
2026-06-18 13:20 ` [qemu-web PATCH v2 2/3] contribute: add automated tool disclosure to bug reporting Daniel P. Berrangé
2026-06-18 13:41 ` Alex Bennée
2026-06-18 13:20 ` [qemu-web PATCH v2 3/3] contribute: switch security process to gitlab confidential issues Daniel P. Berrangé
2026-06-18 13:42 ` Alex Bennée [this message]
2026-06-18 14:07 ` Philippe Mathieu-Daudé
2026-06-18 14:20 ` Daniel P. Berrangé
2026-06-18 14:28 ` Philippe Mathieu-Daudé
2026-06-18 14:42 ` Michael S. Tsirkin
2026-06-18 15:06 ` Daniel P. Berrangé
2026-06-18 15:51 ` Michael S. Tsirkin
2026-06-18 14:49 ` Mauro Matteo Cascella
2026-06-18 15:30 ` Michael S. Tsirkin
2026-06-18 16:07 ` Daniel P. Berrangé
2026-06-18 16:23 ` Michael S. Tsirkin
2026-06-18 16:33 ` Daniel P. Berrangé
2026-06-18 16:39 ` Michael S. Tsirkin
2026-06-18 16:55 ` Daniel P. Berrangé
2026-06-18 17:03 ` Michael S. Tsirkin
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=87qzm4ezho.fsf@draig.linaro.org \
--to=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=mcascell@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=pierrick.bouvier@oss.qualcomm.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@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.