From owner-freebsd-standards@freebsd.org  Thu Jun  4 18:10:45 2020
Return-Path: <owner-freebsd-standards@freebsd.org>
Delivered-To: freebsd-standards@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 4306A32BA8B
 for <freebsd-standards@mailman.nyi.freebsd.org>;
 Thu,  4 Jun 2020 18:10:45 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org
 [IPv6:2610:1c1:1:606c::50:13])
 by mx1.freebsd.org (Postfix) with ESMTP id 49dDNP17Tfz4Rcm
 for <freebsd-standards@freebsd.org>; Thu,  4 Jun 2020 18:10:45 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: by mailman.nyi.freebsd.org (Postfix)
 id 24FFF32B2FC; Thu,  4 Jun 2020 18:10:45 +0000 (UTC)
Delivered-To: standards@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 24C0832B2FB
 for <standards@mailman.nyi.freebsd.org>; Thu,  4 Jun 2020 18:10:45 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org
 [IPv6:2610:1c1:1:606c::19:3])
 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
 key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256
 client-signature RSA-PSS (4096 bits) client-digest SHA256)
 (Client CN "mxrelay.nyi.freebsd.org",
 Issuer "Let's Encrypt Authority X3" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 49dDNP0Ftwz4S22
 for <standards@FreeBSD.org>; Thu,  4 Jun 2020 18:10:45 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2610:1c1:1:606c::50:1d])
 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
 key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256)
 (Client did not present a certificate)
 by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 041A323841
 for <standards@FreeBSD.org>; Thu,  4 Jun 2020 18:10:45 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org ([127.0.1.5])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 054IAiWT013756
 for <standards@FreeBSD.org>; Thu, 4 Jun 2020 18:10:44 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
Received: (from bugzilla@localhost)
 by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 054IAi5A013749
 for standards@FreeBSD.org; Thu, 4 Jun 2020 18:10:44 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
X-Authentication-Warning: kenobi.freebsd.org: bugzilla set sender to
 bugzilla-noreply@freebsd.org using -f
From: bugzilla-noreply@freebsd.org
To: standards@FreeBSD.org
Subject: [Bug 246412] Return EISDIR when reading a directory
Date: Thu, 04 Jun 2020 18:10:44 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: CURRENT
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: commit-hook@freebsd.org
X-Bugzilla-Status: In Progress
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: kevans@freebsd.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-246412-99-Y1TMeLDMTK@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-246412-99@https.bugs.freebsd.org/bugzilla/>
References: <bug-246412-99@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-standards@freebsd.org
X-Mailman-Version: 2.1.33
Precedence: list
List-Id: Standards compliance <freebsd-standards.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-standards>, 
 <mailto:freebsd-standards-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-standards/>
List-Post: <mailto:freebsd-standards@freebsd.org>
List-Help: <mailto:freebsd-standards-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-standards>, 
 <mailto:freebsd-standards-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Jun 2020 18:10:45 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D246412

--- Comment #3 from commit-hook@freebsd.org ---
A commit references this bug:

Author: kevans
Date: Thu Jun  4 18:09:57 UTC 2020
New revision: 361798
URL: https://svnweb.freebsd.org/changeset/base/361798

Log:
  vfs: add restrictions to read(2) of a directory [1/2]

  Historically, we've allowed read() of a directory and some filesystems wi=
ll
  accommodate (e.g. ufs/ffs, msdosfs). From the history department staffed =
by
  Warner: <<EOF

  pdp-7 unix seemed to allow reading directories, but they were weird, spec=
ial
  things there so I'm unsure (my pdp-7 assembler sucks).

  1st Edition's sources are lost, mostly. The kernel allows it. The
  reconstructed sources from 2nd or 3rd edition read it though.

  V6 to V7 changed the filesystem format, and should have been a warning, b=
ut
  reading directories weren't materially changed.

  4.1b BSD introduced readdir because of UFS. UFS broke all directory readi=
ng
  programs in 1983. ls, du, find, etc all had to be rewritten. readdir() and
  friends were introduced here.

  SysVr3 picked up readdir() in 1987 for the AT&T fork of Unix. SysVr4 upda=
ted
  all the directory reading programs in 1988 because different filesystem
  types were introduced.

  In the 90s, these interfaces became completely ubiquitous as PDP-11s runn=
ing
  V7 faded from view and all the folks that initially started on V7 upgraded
  to SysV. Linux never supported this (though I've not done the software
  archeology to check) because it has always had a pathological diversity of
  filesystems.
  EOF

  Disallowing read(2) on a directory has the side-effect of masking
  application bugs from relying on other implementation's behavior
  (e.g. Linux) of rejecting these with EISDIR across the board, but allowing
  it has been a vector for at least one stack disclosure bug in the past[0].

  By POSIX, this is implementation-defined whether read() handles directori=
es
  or not. Popular implementations have chosen to reject them, and this seems
  sensible: the data you're reading from a directory is not structured in s=
ome
  unified way across filesystem implementations like with readdir(2), so it=
 is
  impossible for applications to portably rely on this.

  With this patch, we will reject most read(2) of a dirfd with EISDIR. Users
  that know what they're doing can conscientiously set
  bsd.security.allow_read_dir=3D1 to allow read(2) of directories, as it has
  proven useful for debugging or recovery. A future commit will further lim=
it
  the sysctl to allow only the system root to read(2) directories, to make =
it
  at least relatively safe to leave on for longer periods of time.

  While we're adding logic pertaining to directory vnodes to vn_io_fault, an
  additional assertion has also been added to ensure that we're not reaching
  vn_io_fault with any write request on a directory vnode. Such request wou=
ld
  be a logical error in the kernel, and must be debugged rather than allowi=
ng
  it to potentially silently error out.

  Commented out shell aliases have been placed in root's chsrc/shrc to prom=
ote
  awareness that grep may become noisy after this change, depending on your
  usage.

  A tentative MFC plan has been put together to try and make it as trivial =
as
  possible to identify issues and collect reports; note that this will be
  strongly re-evaluated. Tentatively, I will MFC this knob with the default=
 as
  it is in HEAD to improve our odds of actually getting reports. The future
  priv(9) to further restrict the sysctl WILL NOT BE MERGED BACK, so the kn=
ob
  will be a faithful reversion on stable/12. We will go into the merge
  acknowledging that the sysctl default may be flipped back to restore
  historical behavior at *any* point if it's warranted.

  [0] https://www.freebsd.org/security/advisories/FreeBSD-SA-19:10.ufs.asc

  PR:           246412
  Reviewed by:  mckusick, kib, emaste, jilles, cy, phk, imp (all previous)
  Reviewed by:  rgrimes (latest version)
  MFC after:    1 month (note the MFC plan mentioned above)
  Relnotes:     absolutely, but will amend previous RELNOTES entry
  Differential Revision:        https://reviews.freebsd.org/D24596

Changes:
  head/bin/csh/dot.cshrc
  head/bin/sh/dot.shrc
  head/lib/libc/sys/read.2
  head/sys/kern/vfs_vnops.c

--=20
You are receiving this mail because:
You are on the CC list for the bug.=