From: Andrey Repin <anrdaemon@yandex.ru>
To: Jay Cotton <lbmgmusic@gmail.com>, cygwin@cygwin.com
Subject: Re: Problem with NC.1.107
Date: Wed, 28 Mar 2018 14:20:00 -0000 [thread overview]
Message-ID: <1732290424.20180328171523@yandex.ru> (raw)
In-Reply-To: <CAE=SzZUe8O3q4hnucctrWr=wvJwHszn8XqpqgYOSG6EOxa3iaQ@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=utf-8, Size: 1271 bytes --]
Greetings, Jay Cotton!
> Just installed nc 1.107-4 expecting to use it to debug some code.
> This is what I get when I try to run it.
> $ nc 192.168.1.135 23
> bash: /usr/bin/nc: Permission denied
[C:\Programs\Cygwin_64\bin]$ nc.exe 192.168.1.1 23
âââââââââ¥
Dlink-Router login:
[C:\Programs\Cygwin_64\bin]$
Since nc does not reply to --version, I have no way to tell if it's the same
you are running with.
> The file permissions are messed up.
> $ 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.
> here is the file in /usr/bin
> $ ls -l nc*
> -rwxr-xr-x 1 lbmgm lbmgm 24576 Mar 19 2013 nc.exe
> 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.
--
With best regards,
Andrey Repin
Wednesday, March 28, 2018 17:07:26
Sorry for my terrible english...\x03BKCB\x1cØ\x19[H\x1c\^[Ü\x1cÎ\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0eËØÞYÝÚ[ÛÛKÜ\x1cØ\x19[\Ë\x1d^[[\x03BTN\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0eËØÞYÝÚ[ÛÛKÙ\KÃB^[ØÝ[Y[\x18]\x1a[Û\b\b\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0eËØÞYÝÚ[ÛÛKÙ^[ØÜË\x1d^[[\x03B[ÝXØÜXH\x1a[Î\b\b\b\b\b\x1a\x1d\x1d\x1c\x0eËØÞYÝÚ[ÛÛKÛ[\vÈÝ[ÝXØÜXK\Ú[\^[\x19CBB
next prev parent reply other threads:[~2018-03-28 14:20 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 [this message]
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
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=1732290424.20180328171523@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=cygwin@cygwin.com \
--cc=lbmgmusic@gmail.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).