From owner-freebsd-security Sun Jul 26 17:29:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA04982 for freebsd-security-outgoing; Sun, 26 Jul 1998 17:29:52 -0700 (PDT) (envelope-from owner-freebsd-security@FreeBSD.ORG) Received: from bright.ny.otec.com (bright.ny.otec.com [209.3.16.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA04937 for ; Sun, 26 Jul 1998 17:29:44 -0700 (PDT) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.ny.otec.com (8.8.8/8.8.8) with SMTP id UAA13392; Sun, 26 Jul 1998 20:29:02 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.ny.otec.com: bright owned process doing -bs Date: Sun, 26 Jul 1998 20:29:02 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.ny.otec.com To: Nicholas Charles Brawn cc: freebsd-security@FreeBSD.ORG Subject: Re: preventing fork bombs In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org man login.conf set limits there for login classes. -Alfred On Sun, 26 Jul 1998, Nicholas Charles Brawn wrote: > How can someone limit/prevent fork bomb attacks on your system. I > recently tried one on myself after modifying kern.maxprocperuid (thinking > that should prevent it), and got my machine up to a load of over 150 > before I killed it. > > The simple code used was: > > #include > > main(void) { > while(1) { > fork(); > } > } > > The above effectively freezing my system. :\ > > Anyone got any ideas? > > Nick > > -- > Email: ncb05@uow.edu.au - http://rabble.uow.edu.au/~nick > Key fingerprint = DE 30 33 D3 16 91 C8 8D A7 F8 70 03 B7 77 1A 2A > "When in doubt, ask someone wiser than yourself..." -unknown > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe security" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe security" in the body of the message