> > It would be rather weird to have OpenBSD change the default behavior of > > its netcat version and then see the GNU folks doing the opposite change > > because they prefer it and don't see a need to maintain compatibility > > (which is what the GNU project has done for lots of software). > > > The oldest version of netcat also did not do shutdown on EOF on stdin. > See http://nc110.sourceforge.net/ > > The shutdown behaviour was introduced in our netcat about ten year ago.
That's correct: revision 1.54 date: 2002/12/13 19:53:45; author: aaron; state: Exp; lines: +2 -2 Recent modifications to netcat changed the behaviour to only exit when both the read (network) and write (stdin) ends of the socket were both closed. This is not how nc traditionally works. Instead, revert back to finishing up when read() on the socket returns 0; deraadt@, vincent@ ok. ---------------------------- ... ---------------------------- revision 1.52 date: 2002/07/04 04:42:25; author: vincent; state: Exp; lines: +15 -11 correct handling of EOF on both tty input and network. for example, this allows stuff like nc -l 10101 < /dev/null to have nc exit automatically when it gets EOF from the network. ok ericj@
