Re: Problem with NC.1.107
- Date: Mon, 9 Apr 2018 21:12:01 -0700
- From: Jay Cotton <lbmgmusic@xxxxxxxxx>
- Subject: Re: Problem with NC.1.107
Here is the package listing at cygwin
nc: A simple but powerful network tool (installed binaries and support
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
On Mon, Apr 9, 2018 at 6:51 PM, L A Walsh <cygwin@xxxxxxxxx> wrote:
> Andrey Repin wrote:
>> Greetings, Jay Cotton!
>> Since nc does not reply to --version, I have no way to tell if it's the
>> you are running with.
> That's odd. But has to do with what version of ncat is run.
> I notice my linux machine says:
> nc --version
> Ncat: Version 6.47 ( http://nmap.org/ncat )
> But the version in cygwin:
> cygcheck -f /usr/bin/nc
> is very different. Not sure which is newer or better, but
> the version at nmap.org supports SCTP, though the BSD version
> supports QOS. Not sufficiently versed in either to know
> all the differences. Seems like the nmap.org version has more
> options: 44 vs. BSD's 28 (didn't double count switches from nmap
> that have a short+long form).
> Where do the sources from the BSD version come from? It
> doesn't seem to list a website.
>> The file permissions are messed up.
> I didn't notice this.
>> $ file /usr/bin/nc
>>> /usr/bin/nc: writable, executable, regular file, no read permission
>> I don't see the PE32+ executable (console) x86-64, for MS Windows
> weird -- when I tried that, got:
> file /usr/bin/nc
> /usr/bin/nc: PE32+ executable (console) x86-64 (stripped to external PDB),
> for MS Windows
> here is the file in /usr/bin
>>> $ ls -l nc*
>>> -rwxr-xr-x 1 lbmgm lbmgm 24576 Mar 19 2013 nc.exe
> Looks like the same file I have:
>> ll /usr/bin/nc
> -rwxr-xr-x+ 1 24576 Mar 19 2013 /usr/bin/nc*
> I'm not sure your file command is referencing the same file,
> since my ls shows the same size and date as yours, and clearly
> both show read+execute for U,G and other and write only for owner.
> I looked at the make file, it seems to be o.k. for generating a
>>> runable program. (uses gcc) but I don't have enough stuff installed
>>> to allow a build.
> I think something is wrong with your 'file' command. My nc-binary
> didn't come with a makefile (only binary & manpage):
>> cygcheck -l nc
> 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
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple