4 ms·

> Netcat having being initially written to be used on linux the variants are linux based uh, what? the original netcat was a Unix program, not linux specefic.

by thayne 5y ago

> Netcat having being initially written to be used on linux the variants are linux based uh, what? the original netcat was a Unix program, not linux specefic. I don't think GNU netcat is linux specific either. And the OpenBSD variant, as its name suggests was originally written for OpenBSD, although it was ported to Linux later.

tyingq 5y ago
Yeah, that was funny to me too. Older makefiles had targets for Ultrix, Nextstep, and even Unixware :) https://sourceforge.net/p/nc110/git/ci/v1.10/tree/Makefile https://sourceforge.net/p/nc110/git/ci/v1.10/tree/Makefile
- dsr_ 5y ago
  Hobbit wrote netcat in 1995: https://seclists.org/bugtraq/1995/Oct/28 https://seclists.org/bugtraq/1995/Oct/28
chasil 5y ago
There is also a netcat inside busybox, and the Windows port from frippery.org implements it. The busybox netcat doesn't set off all the malware alarms on my corporate desktop. C:\Temp>\bin\busybox64 nc 1.2.3.4 21 220 (vsFTPd 2.0.5) quit 221 Goodbye. The Windows port is not very smart compared to the rest of the netcat family (the Linux x86-64 version has more of the common options). C:\Temp>\bin\busybox64 nc BusyBox v1.32.0-FRP-3445-g10e14d5eb (2020-04-11 10:50:47 BST) multi-call binary Usage: nc [-l] [-p PORT] [IPADDR PORT] Open a pipe to IP:PORT -l Listen mode, for inbound connects -p PORT Local port
totetsu 5y ago
I think nc works out of the box in MacOS also.
coldtea 5y ago
I think they just wrote Linux to substitute for UNIX in general, as the only UNIX (derivative) that matters. For younger devs, it's all Linux (vs Windows/MacOS/etc). UNIX and its variants is some distant history, like Multics or VMS was to 90s devs. Even FreeBSD is some niche thing they'll seldom, if ever, encounter (much less install). Heck, 20-something year old devs still hadn't reach puberty when SUN still mattered and was a thing.
- indymike 5y ago
  Um. MacOS?
  - coldtea 5y ago
    If you mean "well macOS is a UNIX too", yes. I don't mean younger devs don't use Macs. But for younger devs it's Linux that comes to mind when the context is UNIX-like environment, not the Mac (even though the first is not a UNIX, as it doesn't come from the old UNIX code lineage, and the latter is a certified UNIX). So, they could easily slip and say "netcat or vi was written originally for Linux" (while meaning "for UNIX") versus saying "netcat or vi was written originally for macOS" (which nobody would ever slip and say).
- relaxing 5y ago
  No. Stop. There is no excuse for not knowing one’s history. Especially when making a factual claim like “X was written for Y.”
  - coldtea 5y ago
    There doesn't need to be an excuse. It's enough that it's a reality. People do stuff and don't wait us to excuse them before doing them.

by thayne 5y ago

tyingq 5y ago

Yeah, that was funny to me too. Older makefiles had targets for Ultrix, Nextstep, and even Unixware :) https://sourceforge.net/p/nc110/git/ci/v1.10/tree/Makefile https://sourceforge.net/p/nc110/git/ci/v1.10/tree/Makefile

dsr_ 5y ago
Hobbit wrote netcat in 1995: https://seclists.org/bugtraq/1995/Oct/28 https://seclists.org/bugtraq/1995/Oct/28

chasil 5y ago

There is also a netcat inside busybox, and the Windows port from frippery.org implements it. The busybox netcat doesn't set off all the malware alarms on my corporate desktop. C:\Temp>\bin\busybox64 nc 1.2.3.4 21 220 (vsFTPd 2.0.5) quit 221 Goodbye. The Windows port is not very smart compared to the rest of the netcat family (the Linux x86-64 version has more of the common options). C:\Temp>\bin\busybox64 nc BusyBox v1.32.0-FRP-3445-g10e14d5eb (2020-04-11 10:50:47 BST) multi-call binary Usage: nc [-l] [-p PORT] [IPADDR PORT] Open a pipe to IP:PORT -l Listen mode, for inbound connects -p PORT Local port

totetsu 5y ago

I think nc works out of the box in MacOS also.

coldtea 5y ago

I think they just wrote Linux to substitute for UNIX in general, as the only UNIX (derivative) that matters. For younger devs, it's all Linux (vs Windows/MacOS/etc). UNIX and its variants is some distant history, like Multics or VMS was to 90s devs. Even FreeBSD is some niche thing they'll seldom, if ever, encounter (much less install). Heck, 20-something year old devs still hadn't reach puberty when SUN still mattered and was a thing.

indymike 5y ago
Um. MacOS?
- coldtea 5y ago
  If you mean "well macOS is a UNIX too", yes. I don't mean younger devs don't use Macs. But for younger devs it's Linux that comes to mind when the context is UNIX-like environment, not the Mac (even though the first is not a UNIX, as it doesn't come from the old UNIX code lineage, and the latter is a certified UNIX). So, they could easily slip and say "netcat or vi was written originally for Linux" (while meaning "for UNIX") versus saying "netcat or vi was written originally for macOS" (which nobody would ever slip and say).
relaxing 5y ago
No. Stop. There is no excuse for not knowing one’s history. Especially when making a factual claim like “X was written for Y.”
- coldtea 5y ago
  There doesn't need to be an excuse. It's enough that it's a reality. People do stuff and don't wait us to excuse them before doing them.