Re: ncat 5.10BETA handling of -l -p is not compatible with nc-1.10

[Kris Katterjohn <katterjohn () gmail com>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 01/10/2010 09:57 AM, Denys Vlasenko wrote:
> On Sunday 10 January 2010 09:47, Kris Katterjohn wrote:
> > > Do you understand why compatibility is important?
> > Do you understand why convenience is important?  We as authors and users
> > shouldn't be stuck with command arguments from over a decade ago
>
> You answered my question. You do not understand why compatibility
> is important. Thank God other depelopers do, and, for example,
> coreutils dd is not going to become "more convenient" and ditch
> its "stupid and non-standard" if=FILE style parameters.

I didn't realize the traditional nc was ever as ubiquitous as dd.  Out of
curiosity, how many Linux distros, BSDs and anything else install *Hobbit*'s
nc by default over something like OpenBSD nc?

The notion of overall compatibility between netcats was lost long before Ncat
came along, so it's a little late (and the wrong place) to complain.  Then
again even if I'm wrong and the traditional nc is somehow preferred in popular
distros, etc, the initial point remains that this is ncat, not nc.

Again, Ncat is compatible with and similar to many nc's, including the
traditional.  And scripts already have to take into account the many different
nc's if it uses newer (still years old) features.

And I'm not at all against supporting both -l ways as already suggested.  But
you seem to blindly want complete nc compatibility instead of being happy with
the fix for your whole initial complaint.  David and Fyodor both promptly
responded stating it could be made to work.


Kris Katterjohn

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQIcBAEBAgAGBQJLSgouAAoJEEQxgFs5kUfu+jUQAKJMlrJxfn7lD/JBBC20qXer
hMkP0hPI0LLCHXh7mex/AvYrDo5L+w+LKepP6AsIXcyQZBvicJ73t4ajlahPULeT
Epx1MQ/X5iBUs/ZcS7PyVf7/e64LbQ17XqQeQkq10qguNHh3ev02+4MyNli0J/L3
EIgxUGk7VbTBh+DrIQ1qxx2Fm9niwm9qbtIPrXonmq9eQx0CcOMtrhW2wM4onXTn
CAK8cnuMEkgYKWyxj0XYHoNaN220DB95lSNgv7eJJbRSRWwAs1qcXtCukiOptD/L
tcAjpgh4mxOQFomWLDYpdNAgk1+tRdSDo0wFG13zEKYJEQbjko+SfYrFbjM2WwCD
eqB1wXZxfz98aWcOyiSr7XBoFGJFB2bdNlHJ4tdzJ56VGsX5dGZaC0/XvDnmkvzk
4AniHiB4bDJlaMQIL8nMeKaON1Vh0s5COOzso0Bh9TcD5A3JUQRXlLB7naWLOZQP
loTJ9zmR5V8kdKTci/AP9aRkDTUdZiTip3U9aoinOm0KWGlfYCivERKSUKxNVKRD
wGhvQEYrtDwPP5LPKuht9IR3ATV27fx6K12wLL+acrqX14NZfQ7u4mdDWR7Ou54X
Uuyck4Jm1isJvo4CduYv60GHQhGWHVjREJA+1m7frqKkWE0XS1vmnoNsS/LcNw4U
VhJCoJQYv7e5gl1mPw0P
=M+sc
-----END PGP SIGNATURE-----
_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://seclists.org/nmap-dev/