netdev - Re: Bug with IPv6-UDP address binding

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: <1344512926.28967.743.camel@edumazet-glaptop>
Date:	Thu, 09 Aug 2012 13:48:46 +0200
From:	Eric Dumazet <eric.dumazet@...il.com>
To:	Jesper Dangaard Brouer <brouer@...hat.com>
Cc:	netdev <netdev@...r.kernel.org>, Thomas Graf <tgraf@...g.ch>
Subject: Re: Bug with IPv6-UDP address binding

On Thu, 2012-08-09 at 11:40 +0200, Jesper Dangaard Brouer wrote:

> Guess I should have read Stephens[1] first, as this problem with
> multihomed hosts is described  (on page 219).  He also states, that this
> is a problem/feature related to Berkely-derived implementations.  E.g.
> Solaris handle this, the way I expected. That is, the source IP address
> for the server's reply is the dest IP of the client's request.

Are you sure ?

So Solaris remembers in socket structure the destination IP address of
last UDP message delivered to userland ?

This is not multi thread safe, so it would be a very bad idea.



--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html