From owner-freebsd-current Fri Mar 5 0:50:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from titan.metropolitan.at (unknown [195.212.98.131]) by hub.freebsd.org (Postfix) with ESMTP id D5CCB14FD1 for ; Fri, 5 Mar 1999 00:50:41 -0800 (PST) (envelope-from mladavac@metropolitan.at) Received: by TITAN with Internet Mail Service (5.0.1458.49) id ; Fri, 5 Mar 1999 09:52:42 +0100 Message-ID: <97A8CA5BF490D211A94F0000F6C2E55D097553@s-lmh-wi-900.corpnet.at> From: Ladavac Marino To: 'Peter Jeremy' , dillon@apollo.backplane.com Cc: current@FreeBSD.ORG Subject: RE: Simple DOS against 3.x locks box solid Date: Fri, 5 Mar 1999 09:47:57 +0100 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Peter Jeremy [SMTP:peter.jeremy@auss2.alcatel.com.au] > Sent: Friday, March 05, 1999 4:25 AM > To: dillon@apollo.backplane.com > Cc: current@FreeBSD.ORG > Subject: Re: Simple DOS against 3.x locks box solid > > > As for the general problem, is it sensible to allow a read-only file > to > be mmap'd R/W (with or without MAP_PRIVATE) and then written into? It > would be fairly easy to make mmap() return EACCES if the fd was not > open for writing (or map the memory R/O and SEGV on a write). [ML] Can you say dlopen( "/usr/lib/libc.so")? I thought you could :) Disallow RW MAP_PRIVATE maps of RO files and shared libraries are history. /Marino > Peter > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message