From owner-freebsd-current Wed Mar 17 7:20:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from tsolab.org (dnn.rockefeller.edu [129.85.17.127]) by hub.freebsd.org (Postfix) with ESMTP id 8FB7814CA9; Wed, 17 Mar 1999 07:20:32 -0800 (PST) (envelope-from dan@tsolab.org) Received: from tsolab.org (ts011d14.hil-ny.concentric.net [206.173.17.26]) by tsolab.org (8.8.7/8.8.7) with ESMTP id KAA00470; Wed, 17 Mar 1999 10:20:30 -0500 (EST) (envelope-from dan@tsolab.org) Message-ID: <36EFC7F2.860738C4@tsolab.org> Date: Wed, 17 Mar 1999 10:19:14 -0500 From: Dan Tso Reply-To: dan@tsolab.org Organization: The Rockefeller University X-Mailer: Mozilla 4.05 [en] (Win95; U) MIME-Version: 1.0 To: Dmitry Valdov Cc: freebsd-current@FreeBSD.ORG, freebsd-security@FreeBSD.ORG Subject: Re: disk quota overriding References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dmitry Valdov wrote: > There is a way to overflow / filesystem even is quota is enabled. > > Just make many hard links (for example /bin/sh) to /tmp/ > > for ($q=0;$q<100000;$q++){ > system ("ln /bin/sh /tmp/ln$q"); > } > > Because /tmp directory usually owned by root that why quotas has no effect. > *Directory* size of /tmp can be grown up to available space on / filesystem. > > Any way to fix it? I've always thought that /tmp should be its own filesystem anyways and I generally make it so. Avoids all sorts of nasties. It seems silly to mix up the most vital system files on the same filesystem as the most volitile, damage-prone directory (/tmp). Its better to newfs /tmp regularly. As far as the other issue, the ability to fill up any public 777 directory even with quotas, perhaps the quota system should look at the 1000 bit and do something special with it. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message