netdev - Re: [PATCH 1/1] ipv4: IP_RECVERR should also enqueue source quench messages

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: <20090721.200729.212201103.davem@davemloft.net>
Date:	Tue, 21 Jul 2009 20:07:29 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	hagen@...u.net
Cc:	netdev@...r.kernel.org
Subject: Re: [PATCH 1/1] ipv4: IP_RECVERR should also enqueue source quench
 messages

From: Hagen Paul Pfeifer <hagen@...u.net>
Date: Wed, 22 Jul 2009 01:32:07 +0200

> Currently ICMP source quench messages are silently dropped and not
> enqueued in a per-socket error queue. The socket option IP_RECVERR
> enables a connected datagram socket to notice error conditions received
> via ICMP. This modification allows applications to notice ICMP source
> quench error condition too.
> 
> Side note: source quench are obsolete since day ~0 and are one of the
> early design mistakes of the Internet. Anyway, this does not interfere
> with the fact that a connected socket should not be informed about
> received source quench messages.
> 
> Signed-off-by: Hagen Paul Pfeifer <hagen@...u.net>

I'm almost entirely sure that this behavior is intentional.

All RFCs say to ignore source quench messages with impunity, and Linux
interprets this to mean for our userland interfaces too.

I'm not applying this, sorry.
--
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