| 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: Mon, 20 Aug 2007 16:38:41 +0200 From: "Jesper Juhl" <jesper.juhl@...il.com> To: "Anand Jahagirdar" <anandjigar@...il.com> Cc: "Krzysztof Halasa" <khc@...waw.pl>, linux-kernel@...r.kernel.org Subject: Re: Fork Bombing Patch (please don't top-post) On 20/08/07, Anand Jahagirdar <anandjigar@...il.com> wrote: > Hi > I think Its not worth to make it configurable just for one printk > statement. am i missing something? > I think you are missing the fact that there are lots of situations where users may hit the configured process limit without that being an indication of a fork bomb (or other) attack. This means that there will be many systems that will trigger your warning where there really is no problem. That's a good reason for a) making the message KERN_INFO and b) let administrators somehow disable it completely. Personally I'm wondering if we even want/need this at all. -- Jesper Juhl <jesper.juhl@...il.com> Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html Plain text mails only, please http://www.expita.com/nomime.html - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists