Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Wed, 8 Nov 2017 13:13:20 -0600 (CST)
From: Bob Friesenhahn <>
cc: "Jonas 'Sortie' Termansen" <>
Subject: Re: Race condition between UDP bind(2) and connect(2)
 delivers wrong datagrams

On Wed, 8 Nov 2017, Eric Blake wrote:
>> This issue is not that case because Darwin[1], DragonFly[2], FreeBSD[3],
>> GNU/Hurd (though by importing Linux man pages), Linux[4], NetBSD[5], and
>> OpenBSD[6] all document behavior compatible with POSIX[7].
> It doesn't matter what the implementations document (if their
> documentation is copying from POSIX), but what they actually DO.

For the purpose of this list (about security) it seems to me that the 
current behavior makes use of the recv(2) (or read(2)) system calls 
inherently insecure since there is no way to verify that a received 
message is from the expected source address.  The only work-around is 
to intentionally discard messages until no more messages are 
available, but this may discard valid messages.

This makes most common uses of recv(2) insecure.

Bob Friesenhahn,
GraphicsMagick Maintainer,

Powered by blists - more mailing lists

Please check out the Open Source Software Security Wiki, which is counterpart to this mailing list.

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.