public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Removing netcat from Cygwin
Date: Tue, 16 Feb 2021 10:40:00 -0700	[thread overview]
Message-ID: <39c63dfd-10c5-01b0-d3db-d37d37adb796@SystematicSw.ab.ca> (raw)
In-Reply-To: <DM6PR10MB353096EF5C814F6FB2CDB464B8879@DM6PR10MB3530.namprd10.prod.outlook.com>

On 2021-02-16 10:05, Rodney Kissee via Cygwin wrote:
> My company identifies netcat as a hacking tool and is requiring it to be 
> removed from our version of Cygwin.  How can it be removed or can Cygwin be 
> downloaded without netcat included?
Package netcat is obsolete and has been replaced by nc; more modern replacements 
socat and socat2 support more protocols and faster links; none are base packages 
or dependencies of other packages so must be explicitly requested.

Many programs can be used as hacking tools: they can also be used as recovery 
tools. The above are the software equivalent of patch cables, used to work 
around when some parts of your network are not working because of 
misconfiguration or failure without backup links and you need to recover.

They may be particularly useful if your systems have been pwned by ransomware, 
much of your network is unusable or inaccessible, and your proprietary network 
restore tools don't work on what you still can use.
Worth bearing such considerations in mind in health care organizations. ;^>

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]

      parent reply	other threads:[~2021-02-16 17:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-16 17:05 Rodney Kissee
2021-02-16 17:20 ` Thomas Wolff
2021-02-16 17:35   ` Thomas Wolff
2021-02-16 18:05     ` Marco Atzeri
2021-02-16 17:21 ` matthew patton
2021-02-16 17:29 ` Stephen John Smoogen
2021-02-16 17:39 ` Marco Atzeri
2021-02-16 17:40 ` Brian Inglis [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=39c63dfd-10c5-01b0-d3db-d37d37adb796@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --cc=cygwin@cygwin.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).