Package: netcat-openbsd
Version: 1.130-2
Followup-For: Bug #854292
Dear Maintainer,
I have been hit by this bug twice already since upgrading from 1.130-1
to 1.130-2 (and I expect to run into trouble with libvirt too). In one
case I was able to fix things by using -N iinstead of -q (which being
a new option implies new portability issues).
But does the -q option still do anything at all?
The documentation says:
-q secs quit after EOF on stdin and delay of secs
However it's trivial to see that an EOF does not cause netcat to exit()
and it's not shutting down its socket either since adding -N on the
client-side helps:
$ nc.openbsd -l -p 12345 &
$ echo hello | nc.openbsd -q0 localhost 12345
hello
<...hangs forever...>
$ nc.openbsd -l -p 12345 &
$ echo hello | nc.openbsd -N localhost 12345
hello
Yay! nc.openbsd has quit!
Note that adding -N on the server side does not help:
$ nc.openbsd -l -N -p 12345 &
$ echo hello | nc.openbsd -q0 localhost 12345
hello
<...hangs forever...>
Replace openbsd with traditional and the expected behavior is back.
-- System Information:
Debian Release: 9.0
APT prefers testing
APT policy: (990, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.9.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages netcat-openbsd depends on:
ii libbsd0 0.8.3-1
ii libc6 2.24-9
netcat-openbsd recommends no packages.
netcat-openbsd suggests no packages.
-- no debconf information
