Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.

Re: update netcat 1.11 to netcat 1.12

Skip to first unread message

Ivan Shmakov

Apr 21, 2013, 9:58:13 AM4/21/13
>>>>> 程浩 <> writes:

[Cross-posting to news:comp.protocols.tcp-ip and
news:comp.sources.d, and setting Followup-To: there, for doesn't seem to be an appropriate
newsgroup for Netcat-related discussions in general.]

> update netcat 1.11 to netcat 1.12

Which of the Netcat implementations do you suggest to change?
Please note that there're at least /four/ different Netcats
currently in use, including the "traditional" Netcat,
OpenBSD Netcat, GNU Netcat, and Netcat6. (Cf., e. g., [1].)


> //nc -lp port (remote )
> //nc ip port -e cmd.exe (local)
> //after ctrl+c cmd.exe no exit,socket no shutdown,remote's nc no exit!
> //it is a bug!so write netcat 1.12.

Usually, one doesn't release new versions of the software
without either acquiring the consent of the current maintainer,
or changing the name. Although it's a guideline rather than a
"strict" rule, failure to follow it may result -- and, in this
case, have resulted -- in many distinct versions of the code
being sharing the same name and version. Consider, e. g.:

--cut: --
Here's netcat 1.11 compiled for both 32 and 64-bit Windows (but note
that 64-bit version hasn't been tested much - use at your own risk).

Small update: netcat 1.12 - adds -c command-line option to send CRLF
line endings instead of just CR (eg. to talk to Exchange SMTP)
--cut: --

> //only modify doexec.c by


Please also consider presenting the change in the "Unified diff"
format (cf., e. g., [1]), so that the differences will be easy
to read for anyone concerned.

(I believe that MinGW provides the "diff.exe" version of the
GNU diff program, suitable for the W32 and W64 platforms.)



FSF associate member #7257 np. Returning — Jami Sieber
0 new messages