From: Jay Cotton <lbmgmusic@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Problem with NC.1.107
Date: Tue, 10 Apr 2018 04:12:00 -0000 [thread overview]
Message-ID: <CAE=SzZX4ztqgttxtTh+O08h-4HkK3unrRm_qg573jxj5y-h1kg@mail.gmail.com> (raw)
In-Reply-To: <5ACC18BF.4080904@tlinx.org>
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
On Mon, Apr 9, 2018 at 6:51 PM, L A Walsh <cygwin@tlinx.org> wrote:
> Andrey Repin wrote:
>
>> Greetings, Jay Cotton!
>>
>> Since nc does not reply to --version, I have no way to tell if it's the
>> same
>> 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
>>
> nc-1.107-4
>
> 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
>>> string.
>>>
>> ---
> 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
>>
> /usr/bin/nc.exe
> /usr/share/man/man1/nc.1.gz
>
>
> --
> 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
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 4:12 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 [this message]
2018-04-10 5:54 ` Marco Atzeri
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='CAE=SzZX4ztqgttxtTh+O08h-4HkK3unrRm_qg573jxj5y-h1kg@mail.gmail.com' \
--to=lbmgmusic@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).