From: "Alex Bennée" <alex.bennee@linaro.org>
To: Thomas Huth <thuth@redhat.com>
Cc: qemu-devel@nongnu.org, "Fabiano Rosas" <farosas@suse.de>,
"Peter Xu" <peterx@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Daniel P . Berrangé" <berrange@redhat.com>
Subject: Re: [PATCH] tests: Replace ncat with socat in migration test and drop ncat from containers
Date: Fri, 20 Mar 2026 15:41:30 +0000 [thread overview]
Message-ID: <87se9uv785.fsf@draig.linaro.org> (raw)
In-Reply-To: <20260316183016.239526-1-thuth@redhat.com> (Thomas Huth's message of "Mon, 16 Mar 2026 19:30:16 +0100")
Thomas Huth <thuth@redhat.com> writes:
> From: Thomas Huth <thuth@redhat.com>
>
> nmap / ncat has a somewhat problematic license (e.g. saying claiming
> that derived work is also considered for software that "is designed
> specifically to execute Covered Software and parse the results", e.g.
> by executing ncat from your own program, you might already fall into
> this category) - so for example in openSUSE 16, you can only find it
> in the "non-OSS" repository.
>
> We are currently only using it in the migration functional test, and
> that likely does not fall into this "derived work" category yet (since
> it is also doing some other stuff), but still, to be safe, we should
> move away from using it now.
>
> Unfortunately, switching to one of the other flavors of netcat is
> also not a real option (see commit f700abbbeb6ab68a3446d1fb168a934d),
> but socat should be a solid replacement here instead.
>
> To avoid that someone else easily uses ncat again, let's also remove
> it from our container files now.
>
> Suggested-by: Daniel P. Berrangé <berrange@redhat.com>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
Queued to testing/next, thanks.
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
prev parent reply other threads:[~2026-03-20 15:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-16 18:30 [PATCH] tests: Replace ncat with socat in migration test and drop ncat from containers Thomas Huth
2026-03-16 18:37 ` Philippe Mathieu-Daudé
2026-03-16 19:30 ` Peter Xu
2026-03-20 15:41 ` Alex Bennée [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=87se9uv785.fsf@draig.linaro.org \
--to=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=farosas@suse.de \
--cc=peterx@redhat.com \
--cc=philmd@linaro.org \
--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.