All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org,
	qemu-stable@nongnu.org, stefanha@redhat.com,
	Pierrick Bouvier <pierrick.bouvier@oss.qualcomm.com>
Subject: Re: [PATCH v3 1/6] docs: Mention security considerations for NBD
Date: Tue, 10 Nov 2026 16:10:30 +0000	[thread overview]
Message-ID: <avNB9uLJu7Cn0bbE@redhat.com> (raw)
In-Reply-To: <20261110155356.1520433-7-eblake@redhat.com>

On Tue, Nov 10, 2026 at 09:53:57AM -0600, Eric Blake wrote:
> Document a policy that NBD connections should strongly consider using
> TLS and x509 certificates to filter out unwanted clients.  If a
> malicious server or client can trigger a QEMU assertion failure on a
> plaintext connection, but can trivially have risk mitigated by
> enabling TLS to weed out unknown partners (so that a full-on attack of
> QEMU would first require chaining some other attack to convince a
> "trusted" client to break protocol in the first place), then that
> reduces the CVSS-BE score of the QEMU bug. In turn, our policy already
> states that low severity scores can be fixed without an embargo.
> 
> Signed-off-by: Eric Blake <eblake@redhat.com>
> 
> ---
> v3: more wording tweaks, since even a TLS-authorized partner cannot
> be considered 100% trusted, but is reduced risk.
> ---
>  docs/system/security.rst | 23 +++++++++++++++++++++++
>  1 file changed, 23 insertions(+)

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 :|



  parent reply	other threads:[~2026-11-10 16:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-10 15:30 [PATCH for-11.2 v3 0/6] Fix some low-severity NBD CVEs Eric Blake
2026-11-10 15:53 ` [PATCH v3 1/6] docs: Mention security considerations for NBD Eric Blake
2026-11-10 15:53   ` [PATCH v3 2/6] iotests: Refactor python NBD server setup Eric Blake
2026-11-10 16:11     ` Daniel P. Berrangé
2026-11-10 15:53   ` [PATCH v3 3/6] nbd/server: Reject rather than assert on non-compliant BLOCK_STATUS Eric Blake
2026-11-10 16:12     ` Daniel P. Berrangé
2026-11-10 15:54   ` [PATCH v3 4/6] iotests: Add new nbd-robustness test Eric Blake
2026-11-10 15:54   ` [PATCH v3 5/6] nbd/server: Reject rather than assert on non-compliant NBD_OPT_SET_META_CONTEXT Eric Blake
2026-11-10 16:19     ` Daniel P. Berrangé
2026-11-10 15:54   ` [PATCH v3 6/6] iotests: Add another nbd-robustness test Eric Blake
2026-11-10 16:10   ` Daniel P. Berrangé [this message]
2026-11-10 16:27 ` [PATCH for-11.2 v3 0/6] Fix some low-severity NBD CVEs 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=avNB9uLJu7Cn0bbE@redhat.com \
    --to=berrange@redhat.com \
    --cc=eblake@redhat.com \
    --cc=pierrick.bouvier@oss.qualcomm.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@nongnu.org \
    --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.