From: Christian Schoenebeck <qemu_oss@crudebyte.com>
To: qemu-devel@nongnu.org
Cc: "Greg Kurz" <groug@kaod.org>,
"Daniel P. Berrangé" <berrange@redhat.com>
Subject: Re: [PATCH v5] 9pfs: deprecate 'proxy' backend
Date: Thu, 29 Jun 2023 12:07:43 +0200 [thread overview]
Message-ID: <9758911.ANVE0QeqSM@silver> (raw)
In-Reply-To: <E1qDkmw-0007M1-8f@lizzy.crudebyte.com>
On Monday, June 26, 2023 1:49:06 PM CEST Christian Schoenebeck wrote:
> As recent CVE-2023-2861 (fixed by f6b0de53fb) once again showed, the 9p
> 'proxy' fs driver is in bad shape. Using the 'proxy' backend was already
> discouraged for safety reasons before and we recommended to use the
> 'local' backend (preferably in conjunction with its 'mapped' security
> model) instead, but now it is time to officially deprecate the 'proxy'
> backend.
>
> Signed-off-by: Christian Schoenebeck <qemu_oss@crudebyte.com>
> Reviewed-by: Greg Kurz <groug@kaod.org>
> ---
> v4 -> v5:
> - Eliminate repititve use of word 'instead' in text.
> - Commit log: mention exact commit which fixed CVE-2023-2861.
Queued on 9p.next:
https://github.com/cschoenebeck/qemu/commits/9p.next
Thanks!
Best regards,
Christian Schoenebeck
prev parent reply other threads:[~2023-06-29 10:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-26 11:49 [PATCH v5] 9pfs: deprecate 'proxy' backend Christian Schoenebeck
2023-06-29 10:07 ` Christian Schoenebeck [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=9758911.ANVE0QeqSM@silver \
--to=qemu_oss@crudebyte.com \
--cc=berrange@redhat.com \
--cc=groug@kaod.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;
as well as URLs for NNTP newsgroup(s).