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
| ||
|
Date: Sat, 17 Apr 2021 09:50:30 +0200 From: Willy Tarreau <w@....eu> To: Keyu Man <kman001@....edu> Cc: Eric Dumazet <edumazet@...gle.com>, David Ahern <dsahern@...il.com>, Florian Westphal <fw@...len.de>, davem@...emloft.net, yoshfuji@...ux-ipv6.org, dsahern@...nel.org, Jakub Kicinski <kuba@...nel.org>, netdev@...r.kernel.org, linux-kernel@...r.kernel.org, Zhiyun Qian <zhiyunq@...ucr.edu> Subject: Re: PROBLEM: DoS Attack on Fragment Cache On Sat, Apr 17, 2021 at 12:42:39AM -0700, Keyu Man wrote: > How about at least allow the existing queue to finish? Currently a tiny new > fragment would potentially invalid all previous fragments by letting them > timeout without allowing the fragments to come in to finish the assembly. Because this is exactly the principle of how attacks are built: reserve resources claiming that you'll send everything so that others can't make use of the resources that are reserved to you. The best solution precisely is *not* to wait for anyone to finish, hence *not* to reserve valuable resources that are unusuable by others. Willy
Powered by blists - more mailing lists