From: Peter Maydell <peter.maydell@linaro.org>
To: "Marc-André Lureau" <marcandre.lureau@redhat.com>
Cc: Samuel Thibault <samuel.thibault@ens-lyon.org>,
Jason Wang <jasowang@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [PATCH] RFC: net: document "-netdev user" explicitly as unsafe
Date: Mon, 7 Jun 2021 13:06:34 +0100 [thread overview]
Message-ID: <CAFEAcA-sQzZ2DFeqEU19W1h=SL2WsTwnAYSEJUomM_Yxk5Sf3w@mail.gmail.com> (raw)
In-Reply-To: <20210607114844.2015685-1-marcandre.lureau@redhat.com>
On Mon, 7 Jun 2021 at 12:50, <marcandre.lureau@redhat.com> wrote:
>
> From: Marc-André Lureau <marcandre.lureau@redhat.com>
>
> libslirp is known to have several security flaws, we should make it
> explicit by warning the users and in the documentation.
>
> Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>
> --- a/net/slirp.c
> +++ b/net/slirp.c
> @@ -388,6 +388,8 @@ static int net_slirp_init(NetClientState *peer, const char *model,
> char *end;
> struct slirp_config_str *config;
>
> + warn_report("User mode network stack is unsafe!");
Not enthusiastic about generating new warnings for a huge range
of end-users, especially without detailed information about
what they should do about it and suitable new command lines
(including ones which will work for everybody, not just "I'm
on an x86 PC with pluggable network devices").
Also, -net user is perfectly fine for quite a lot of usecases.
thanks
-- PMM
prev parent reply other threads:[~2021-06-07 12:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-07 11:48 [PATCH] RFC: net: document "-netdev user" explicitly as unsafe marcandre.lureau
2021-06-07 12:06 ` Peter Maydell [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='CAFEAcA-sQzZ2DFeqEU19W1h=SL2WsTwnAYSEJUomM_Yxk5Sf3w@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=jasowang@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=samuel.thibault@ens-lyon.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).