From owner-freebsd-hackers Thu Nov 28 07:15:25 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA29747 for hackers-outgoing; Thu, 28 Nov 1996 07:15:25 -0800 (PST) Received: from gatekeeper.alcatel.no (ns0.alcatel.no [193.213.238.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA29741 for ; Thu, 28 Nov 1996 07:15:21 -0800 (PST) Received: from stkd71.alcatel.no by gatekeeper.alcatel.no (8.7.3/Alcanet-SC) id QAA07155; Thu, 28 Nov 1996 16:15:15 +0100 (MET) Received: by stkd71.alcatel.no (5.57/DEC-Ultrix/4.3) id AA22343; Thu, 28 Nov 96 16:14:56 +0100 Message-Id: <329DA7B9.41C67EA6@alcatel.no> Date: Thu, 28 Nov 1996 15:54:49 +0100 From: Arve Ronning X-Mailer: Mozilla 2.02 (X11; I; FreeBSD 2.1.5-RELEASE i386) Mime-Version: 1.0 To: Robert Nordier Cc: hackers@freebsd.org Subject: Re: A simple way to crash your system. References: <199611271737.TAA03168@eac.iafrica.com> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Robert Nordier wrote: > > Bob Bishop wrote: > > Would anyone object to the following? > > By default, msdosfs would in future not mount DOS FSes with a block > size exceeding 32 (or maybe 16) sectors, since these appear to be > the filesystems that trigger the UFS corruption problem. > > However, to revert to present behavior (ie. mount any DOS partition), > either: > > (a) Use mount(8) or mount_msdos(8) with the -f (force) option; or > (b) Specify MSDOSFS_FORCE as a kernel configuration option. > > This should offer some protection to unwary users, but not get in the > way of those who are prepared to take their chances. > Sounds fine to me as this will let me continue using msdosfs for floppies. -Arve—