From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 60036 invoked by alias); 10 Apr 2018 04:12:06 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 59920 invoked by uid 89); 10 Apr 2018 04:12:05 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-5.0 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,GIT_PATCH_2,HK_RANDOM_ENVFROM,HK_RANDOM_FROM,HTML_MESSAGE,KAM_NUMSUBJECT,KAM_SHORT,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=listing, H*c:alternative X-HELO: mail-it0-f47.google.com Received: from mail-it0-f47.google.com (HELO mail-it0-f47.google.com) (209.85.214.47) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 10 Apr 2018 04:12:03 +0000 Received: by mail-it0-f47.google.com with SMTP id 71-v6so13112029ith.2 for ; Mon, 09 Apr 2018 21:12:03 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=4vyv5qiVRzLOTvP++hwQMUMzKIN6DrMmII6VMAohbY0=; b=CXbVw4tlWJ2JYFwp3uXhsBPVBa9sLzfI/yMDly5n1WBRzM5cCIYJqSui+hCzF9j/cZ JEgNZqINlOM5bE04VdMkkh2ySPJsGq3yHg+E2fL/G68jvZXSqzDpBZ1sYJRMbLeGiXcr mhhKlwdx3+/I6JRcjYMreJu68+13J/wEtL5WE9/tfAE1popTU8KQX5xkliY2Gg4JjOk0 HDgOIutGVI476cSaRONle5wgsbllZRXYTSxVptZmEGxNz2lH5TiFJd0bdh9NNRy6f1vk 4vDgRO986yM7ebyVS5UpfsNZ1/SKK4wYPr1E9NLkpcQgDJNTzJV0kHLw22PEoD0dTasD 1RvQ== X-Gm-Message-State: ALQs6tBy+RxlQM07kWmqhFqi0OPgy0cMqyxYIIpVsYJoFTQZiMYBNf8r tnccxoQPpDog0Vb1NedT3bn8X4TnkwXuOENPKGtkDw== X-Google-Smtp-Source: AIpwx4/thrKvBs6xsPV4ToYq/XdW73IhKrUPHPWoJSSSoBOxksnHFN5ujXgjyHSarrhTgymfwqrAiUWTD8g3tsnM58U= X-Received: by 2002:a24:5081:: with SMTP id m123-v6mr543365itb.118.1523333521649; Mon, 09 Apr 2018 21:12:01 -0700 (PDT) MIME-Version: 1.0 Received: by 10.79.243.57 with HTTP; Mon, 9 Apr 2018 21:12:01 -0700 (PDT) In-Reply-To: <5ACC18BF.4080904@tlinx.org> References: <1732290424.20180328171523@yandex.ru> <5ACC18BF.4080904@tlinx.org> From: Jay Cotton Date: Tue, 10 Apr 2018 04:12:00 -0000 Message-ID: Subject: Re: Problem with NC.1.107 To: cygwin@cygwin.com Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes X-SW-Source: 2018-04/txt/msg00089.txt.bz2 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 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