netdev - Re: [PATCH] net/core: Make urgent data inline by default

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] [day] [month] [year] [list]

Date:	Tue, 5 Jul 2011 08:41:50 +0300
From:	Esa-Pekka Pyokkimies <esa-pekka.pyokkimies@...nesoft.com>
To:	David Miller <davem@...emloft.net>
CC:	<netdev@...r.kernel.org>
Subject: Re: [PATCH] net/core: Make urgent data inline by default

On Tue, 05 Jul 2011 02:38:38 +0300, David Miller <davem@...emloft.net>  
wrote:

> There is no way we can make this change, we've had the default
> we currently have for 18+ years.  Breaking applications is a
> very real possibility.
>
> It doesn't matter what some RFC says.

I understand. However urgent pointer is a very niche feature and I don't  
think
it would really break much. FTP and telnet both want the urgent data inline
anyway. I haven't found any application which uses the "1-byte" urgent  
data,
which can by some change be overwritten by the next urgent data if you  
didn't
read it in time. The reason I would want this change is that attack  
detection
is very difficult when there can be a byte missing due to URG flag being  
set,
and the damage done by crackers is more than the damage to applications I  
think.
But I guess you decide. Atleast I tried.

Esa-Pekka
--
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