From owner-freebsd-bugs Fri Jun 7 22: 0:37 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id D8F7C37B409 for ; Fri, 7 Jun 2002 22:00:05 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g58505672099; Fri, 7 Jun 2002 22:00:05 -0700 (PDT) (envelope-from gnats) Date: Fri, 7 Jun 2002 22:00:05 -0700 (PDT) Message-Id: <200206080500.g58505672099@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Bruce Evans Subject: Re: kern/38986: a change to msdosfs permissions behaviour according to noexec Reply-To: Bruce Evans Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR kern/38986; it has been noted by GNATS. From: Bruce Evans To: neologism Cc: freebsd-gnats-submit@FreeBSD.ORG Subject: Re: kern/38986: a change to msdosfs permissions behaviour according to noexec Date: Sat, 8 Jun 2002 14:59:20 +1000 (EST) On Fri, 7 Jun 2002, neologism wrote: > On Fri, Jun 07, 2002 at 05:15:52PM +0100, Ceri Davies wrote: > > On Fri, Jun 07, 2002 at 12:43:56PM +0200, neologism wrote: > > > > > > Current implementation of permission checking in msdosfs doesn't reflect > > > setting of noexec at mount time. I'm sending a patch which changes this > > > behaviour. Now if noexec is set rights are set to 644 instead of 755. > > > I hope its done the right way. > > > > Note that I'm not disputing this patch, I just wonder if it's necessary or > > just adding more strangeness to msdos filesystems. > > it's very small so I consider it no problem > > > Mounting an ffs filesystem noexec doesn't do this - is there any reason why > > msdosfs ones should ? > > ffs has permissions unix way, msdosfs doesn't. You simply cannot set > chmod a-x * ! I want this for comfortable MC (midnight commander) browsing > through files. You know click enter on .gz file opens it. If it is not +x. > But if it hurts so much... > > > Just something for whoever may want to commit this to think about. This has been thought about before in response to a patch like the one in this PR, resulting in a better patch in PR 35699 (don't make mount -noexec affect permissions, since it doesn't for real filesystems, but work around the fundamental limitations of the -m flag by adding a -M flag to control the mode of directories). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message