From owner-freebsd-bugs Fri Jun 7 9:20: 7 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 9A3FD37B405 for ; Fri, 7 Jun 2002 09:20:03 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g57GK3B39151; Fri, 7 Jun 2002 09:20:03 -0700 (PDT) (envelope-from gnats) Date: Fri, 7 Jun 2002 09:20:03 -0700 (PDT) Message-Id: <200206071620.g57GK3B39151@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Ceri Davies Subject: Re: kern/38986: a change to msdosfs permissions behaviour according to noexec Reply-To: Ceri Davies 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: Ceri Davies To: neologism Cc: FreeBSD-gnats-submit@FreeBSD.org Subject: Re: kern/38986: a change to msdosfs permissions behaviour according to noexec Date: Fri, 7 Jun 2002 17:15:52 +0100 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. Mounting an ffs filesystem noexec doesn't do this - is there any reason why msdosfs ones should ? Just something for whoever may want to commit this to think about. Ceri To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message