public inbox for
 help / color / mirror / Atom feed
From: Brian Inglis <>
Subject: Re: Problem with NC.1.107
Date: Fri, 13 Apr 2018 12:29:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 2018-04-13 02:44, L A Walsh wrote:
> Jay Cotton wrote:
> You said:
>> I don't see the PE32+ executable (console) x86-64, for MS Windows
>>> >>> string.
> Whereas, when I used the file command, it printed out exactly
> what you were searching for.  Thus my assertion that your file
> command is the likely culprit.
>> file /usr/bin/nc
>> /usr/bin/nc: PE32+ executable (console) x86-64 (stripped to external PDB),
>> for MS Windows
> As for the not-executable error message, have you checked,
> as suggested elsewhere, whether or not you have some cheap
> anti-virus installed that blocks programs that are not viruses
> like 'nc'?

$ which file nc | xargs ls -glo
-rwxr-xr-x 1 22035 Mar 18 08:18 /usr/bin/file
-rwxr-xr-x 1 24576 Mar 19  2013 /usr/bin/nc
$ which file nc | xargs file
/usr/bin/file: PE32+ executable (console) x86-64, for MS Windows
/usr/bin/nc:   PE32+ executable (console) x86-64 (stripped to external PDB), for
MS Windows
$ printf "HEAD / HTTP/1.0\r\n\r\n" | nc 80
HTTP/1.1 200 OK
Date: Fri, 13 Apr 2018 11:45:41 GMT
Server: Apache
Accept-Ranges: bytes
Vary: Accept-Encoding
Content-Security-Policy: default-src 'self' http: https:
Connection: close
Content-Type: text/html; charset=UTF-8

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

Problem reports:
Unsubscribe info:

      reply	other threads:[~2018-04-13 12:29 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
2018-04-13  8:45       ` L A Walsh
2018-04-13 12:29         ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).