netdev - Re: EINVAL when using connect() for udp sockets

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAEnbY+fPLamzXF8nOF-SEFE8LaE88XAyKNt81zs6bM866R4oGg@mail.gmail.com>
Date:   Thu, 23 Mar 2017 13:22:28 +1100
From:   Daurnimator <quae@...rnimator.com>
To:     netdev@...r.kernel.org
Cc:     William Ahern <william@...handclement.com>,
        "Santi T." <santitm99@...il.com>
Subject: Re: EINVAL when using connect() for udp sockets

On 9 March 2017 at 14:10, Daurnimator <quae@...rnimator.com> wrote:
> When debugging https://github.com/daurnimator/lua-http/issues/73 which
> uses https://github.com/wahern/dns we ran into an issue where modern
> linux kernels return EINVAL if you try and re-use a udp socket.
> The issue seems to occur if you go from a local destination ip to a
> non-local one.

Did anyone get a chance to look into this issue?