public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Jonatan Schlag <jonatan.schlag@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: gnu-netcat
Date: Sun, 27 Nov 2022 14:24:42 +0100	[thread overview]
Message-ID: <79DA000B-4D62-4230-B1DB-EB90F454EB9D@ipfire.org> (raw)
In-Reply-To: <3896B39D-1166-4A2F-B826-646009D518AB@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 982 bytes --]

Hi *,

In my memories, it was the other way around.  We have and ncat for libvirtd because gnu-netcat doesn’t support sockets. So I am fine with dropping this. 

Jonatan 

> Am 27.11.2022 um 13:10 schrieb Michael Tremer <michael.tremer(a)ipfire.org>:
> 
> Hello Adolf,
> 
> If I remember this correctly, we have gnu-netcat because libvirtd only works with that one.
> 
> Jonatan might now. I copied him in the hope he will see this email.
> 
> -Michael
> 
>> On 24 Nov 2022, at 17:48, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>> 
>> Dear All,
>> 
>> IPFire has nmap/ncat as an addon which is under ongoing development.
>> 
>> I have noticed that we also have gnu-netcat as an addon, which was last updated in 2004.
>> 
>> Do we need to have gnu-netcat from 2004 when we have nmap/ncat.
>> 
>> 
>> If the decision is that we don't need it then I would raise a patch to remove it from IPFire.
>> 
>> 
>> Regards,
>> 
>> Adolf.
>> 
>> 
> 

      reply	other threads:[~2022-11-27 13:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-24 17:48 gnu-netcat Adolf Belka
2022-11-27 12:10 ` gnu-netcat Michael Tremer
2022-11-27 13:24   ` Jonatan Schlag [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=79DA000B-4D62-4230-B1DB-EB90F454EB9D@ipfire.org \
    --to=jonatan.schlag@ipfire.org \
    --cc=development@lists.ipfire.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