From owner-freebsd-hackers@freebsd.org Fri May 15 19:49:34 2020 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 1DB5F2FEC07 for ; Fri, 15 May 2020 19:49:34 +0000 (UTC) (envelope-from bsd-lists@BSDforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ultimatedns.net", Issuer "Let's Encrypt Authority X3" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 49NzWd52fjz4MRv; Fri, 15 May 2020 19:49:33 +0000 (UTC) (envelope-from bsd-lists@BSDforge.com) Received: from udns.ultimatedns.net (localhost [IPv6:0:0:0:0:0:0:0:1]) by udns.ultimatedns.net (8.15.2/8.15.2) with ESMTPS id 04FJnobC057377 (version=TLSv1.2 cipher=DHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Fri, 15 May 2020 12:49:56 -0700 (PDT) (envelope-from bsd-lists@BSDforge.com) X-Mailer: Cypht MIME-Version: 1.0 Cc: FreeBSD Hackers In-Reply-To: From: Chris Reply-To: bsd-lists@BSDforge.com To: Ed Maste Subject: Re: [HEADSUP] Disallowing read() of a directory fd Date: Fri, 15 May 2020 12:49:56 -0700 Message-Id: <34b419c93394e7b933b3edcb43244a4d@udns.ultimatedns.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 49NzWd52fjz4MRv X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-1.48 / 15.00]; NEURAL_HAM_MEDIUM(-0.51)[-0.508,0]; NEURAL_HAM_LONG(-0.98)[-0.975,0]; ASN(0.00)[asn:11404, ipnet:24.113.0.0/16, country:US]; local_wl_ip(0.00)[24.113.41.81] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 May 2020 19:49:34 -0000 On Fri, 15 May 2020 13:49:54 -0400 Ed Maste emaste@freebsd=2Eorg said > On Fri, 15 May 2020 at 13:14, Chris wrote: > > > > But given the potential > > gains for all this, are trivial at best=2E In a purely observational view=2E=2E=2E >=20 > Some benefits of this change have already been discussed: > 1=2E It would have prevented, or at least significantly blunted, the > security issue described in FreeBSD-SA-19:10=2Eufs=2E > 2=2E It avoids problems caused by application assumptions=2E Applications that fail in this regard, are poorly designed, and need to step up=2E It's not up to (Free)BSD to bend to their lazyness=2E >=20 > On the other hand, arguments for allowing reads of directories: > 1=2E It's always been that way=2E > 2=2E File system developers and experts may use the ability for certain > special or unusual actions=2E >=20 > Making the change with a sysctl to control still allows the special > case use, and I'm glad that Kyle spent the time on this change=2E I too conceded to this perhaps being a reasonable approach=2E So long as it wasn't read-only=2E In the end; given that there was a non perceivable amount of noise on this over the last 40 some yrs=2E It hardly seemed worth/any effort(s)=2E -- observationally speaking; not emotionally :-) --Chris