From owner-freebsd-security Tue Jul 10 20:54:34 2001 Delivered-To: freebsd-security@freebsd.org Received: from rlee.leefam.org (cx250485-a.irvn1.occa.home.com [24.19.255.190]) by hub.freebsd.org (Postfix) with ESMTP id 927FC37B405 for ; Tue, 10 Jul 2001 20:54:30 -0700 (PDT) (envelope-from rel@gulbransen.com) Received: from localhost (rel@localhost [127.0.0.1]) by rlee.leefam.org (8.11.4/8.9.3) with ESMTP id f6B3sLW00322; Tue, 10 Jul 2001 20:54:22 -0700 (PDT) (envelope-from rel@gulbransen.com) Date: Tue, 10 Jul 2001 20:54:19 -0700 (PDT) From: "Robert E. Lee" X-X-Sender: To: Dag-Erling Smorgrav Cc: Ted Mittelstaedt , , Subject: Re: Kernel Panic In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On 24 Jun 2001, Dag-Erling Smorgrav wrote: > "Ted Mittelstaedt" writes: > A disk error would not crash the system. Please stop spouting > unfounded (though highly imaginative) bullshit. Not to get into a pissing contest, but I have had disk errors in the past that made my system crash. On the original thread, when you have a local account on a box, you can usually use this script as an effective DoS: $ more foo.sh #!/bin/sh while [ 1 -eq 1 ]; do find / -name foo & done The default settings for most Unix OS's allow that type of script to consume enough resources to make the system unusable. Robert E. Lee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message