astian:
> astian:
>>> AFAICT it's a no-op for stream sockets; might make sense to error
>>> out unless ‘-u’ is set.
>>
>> Right, so it could be something like:
>>
>> -} else if (argc == 1 && !pflag && !sflag) {
>> +} else if (argc == 1 && !pflag && (!sflag || (family == AF_UNIX &&
>>
astian:
>> AFAICT it's a no-op for stream sockets; might make sense to error
>> out unless ‘-u’ is set.
>
> Right, so it could be something like:
>
> - } else if (argc == 1 && !pflag && !sflag) {
> + } else if (argc == 1 && !pflag && (!sflag || (family == AF_UNIX &&
> uflag))) {
>
> Or
Guilhem Moulin:
> On Sat, 24 Aug 2019 at 20:25:00 +, astian wrote:
>> Looking at the patch I don't trust this is the only behaviour change. I
>> don't understand why this divergence from upstream was introduced and I
>> wish it was reverted altogether.
>
> The patch was added to support the
Control: retitle -1 netcat-openbsd: Unable to specify client socket for
UNIX-domain datagram sockets
Control: found -1 1.187-1
Control: found -1 1.195-2
Hi,
On Sat, 24 Aug 2019 at 20:25:00 +, astian wrote:
> Looking at the patch I don't trust this is the only behaviour change. I
> don't
Package: netcat-openbsd
Version: 1.203-1
Severity: normal
Control: tags -1 + patch
Dear Maintainer,
The debian-specific patch "use-flags-to-specify-listen-address.patch"
disallows the usage of "-s" in some valid cases. For example, the
following should connect to the unix socket "target" and
5 matches
Mail list logo
