From owner-freebsd-security Wed Sep 1 14: 9:19 1999 Delivered-To: freebsd-security@freebsd.org Received: from thetis.deor.org (thetis.quickie.net [206.245.163.5]) by hub.freebsd.org (Postfix) with ESMTP id 4347215A83 for ; Wed, 1 Sep 1999 14:09:04 -0700 (PDT) (envelope-from rabbi@quickie.net) Received: from localhost (rabbi@localhost) by thetis.deor.org (8.9.3/8.9.3) with ESMTP id RAA13738; Wed, 1 Sep 1999 17:08:28 -0400 Date: Wed, 1 Sep 1999 17:08:22 -0400 (EDT) From: "L. Sassaman" To: FreeBSD -- The Power to Serve Cc: Jeff Wheat , freebsd-security@FreeBSD.ORG Subject: Re: FW: Local DoS in FreeBSD In-Reply-To: Message-ID: X-AIM: Elom777 X-icq: 10735603 X-No-Archive: yes X-PGP: X-PGP-ID-Fprnt: 0x09AC0A6A 7A1A 407F B1CA 7E4E AE85 E730 3D8A F1B2 09AC 0A6A X-PGP-S: X-PGP-ID-Fprnt-S: 0x3AF92BD0 566B 5CA8 A733 34AA A482 586F 38D9 DBA8 3AF9 2BD0 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 1 Sep 1999, FreeBSD -- The Power to Serve wrote: > If you have public access users, you should have login accounting in the > first place.. and yes, it does stop it :).. I verified this on a 3.2 box > with my login accounting setup.. Okay, tweak the login.conf and you stop users from issuing the attack from the shell. But what about someone who builds the program and uploads it into a cgi-bin? Are we just to stop allowing cgi's to be run if they require higher resource limits? L. Sassaman System Administrator | "Even the most primitive society has Technology Consultant | an innate respect for the insane." icq.. 10735603 | pgp.. finger://ns.quickie.net/rabbi | --Mickey Rourke -----BEGIN PGP SIGNATURE----- Version: GnuPG v0.9.10 (GNU/Linux) Comment: OpenPGP Encrypted Email Preferred. iD8DBQE3zZXMPYrxsgmsCmoRAixFAKD5invyFWxll26tuJxuJ2u7UlNjNQCgiu1b EnM3D/O25Wl+26pXVuRYpWM= =Qeqw -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message