From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Problem with NC.1.107
Date: Tue, 10 Apr 2018 05:54:00 -0000 [thread overview]
Message-ID: <9dd6f36b-d61f-27e8-09e1-8beb39a1dc52@gmail.com> (raw)
In-Reply-To: <CAE=SzZX4ztqgttxtTh+O08h-4HkK3unrRm_qg573jxj5y-h1kg@mail.gmail.com>
On 10/04/2018 06:12, Jay Cotton wrote:
> Here is the package listing at cygwin
>
> nc: A simple but powerful network tool (installed binaries and support
> files)
>
> 2013-03-19 15:35 0 usr/
> 2013-03-19 15:35 0 usr/bin/
> 2013-03-19 15:35 24576 usr/bin/nc.exe
> 2013-03-19 15:35 0 usr/share/
> 2013-03-19 15:35 0 usr/share/man/
> 2013-03-19 15:35 0 usr/share/man/man1/
> 2013-03-19 15:30 5052 usr/share/man/man1/nc.1.gz
>
>
post bottom here, and also trim the reply please.
As I highlighted before, you wrote:
$ nc 192.168.1.135 23
bash: /usr/bin/nc: Permission denied
the message is from bash and it reports that bash can not execute
nc. This happens when a Antivirus denies access to the program.
For example Symantec always blocks any nc.
Please note that nc replies to
$ nc --version
nc: unknown option -- -
usage: nc [-46CDdhklnrtUuvz] [-I length] [-i interval] [-O length]
[-P proxy_username] [-p source_port] [-s source] [-T ToS]
[-V rtable] [-w timeout] [-X proxy_protocol]
[-x proxy_address[:port]] [destination] [port]
Regards
Marco
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2018-04-10 5:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-28 7:09 Jay Cotton
2018-03-28 14:05 ` Marco Atzeri
2018-03-28 14:20 ` Andrey Repin
2018-04-10 1:52 ` L A Walsh
2018-04-10 4:12 ` Jay Cotton
2018-04-10 5:54 ` Marco Atzeri [this message]
2018-04-13 8:45 ` L A Walsh
2018-04-13 12:29 ` Brian Inglis
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=9dd6f36b-d61f-27e8-09e1-8beb39a1dc52@gmail.com \
--to=marco.atzeri@gmail.com \
--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).