From owner-freebsd-bugs@freebsd.org  Fri Oct 20 21:25:03 2017
Return-Path: <owner-freebsd-bugs@freebsd.org>
Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id EB257E404DF
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Fri, 20 Oct 2017 21:25:03 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id D9EAD66666
 for <freebsd-bugs@FreeBSD.org>; Fri, 20 Oct 2017 21:25:03 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v9KLP35u077029
 for <freebsd-bugs@FreeBSD.org>; Fri, 20 Oct 2017 21:25:03 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 223138] null(4) has DIOCSKERNELDUMP ioctl
Date: Fri, 20 Oct 2017 21:25:03 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 11.1-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: freebsd-bugs@maxsi.org
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform
 op_sys bug_status bug_severity priority component assigned_to reporter
Message-ID: <bug-223138-8@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-bugs@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Oct 2017 21:25:04 -0000

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

            Bug ID: 223138
           Summary: null(4) has DIOCSKERNELDUMP ioctl
           Product: Base System
           Version: 11.1-RELEASE
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: kern
          Assignee: freebsd-bugs@FreeBSD.org
          Reporter: freebsd-bugs@maxsi.org

The /dev/null device unusually has a DIOCSKERNELDUMP ioctl that exists on no
other operating system. This ioctl controls kernel crash dumping. What is t=
his
feature doing in this very unexpected place? I haven't checked but I assume=
 the
ioctl requires administrative privileges to use but /dev/null is a strange =
home
for it. I don't believe this has any security implications. It just
unnecessarily expose attack surface since /dev/null objects can commonly be
given to sandboxed environments and is generally considered a certainly ben=
ign
object.

DIOCSKERNELDUMP is not documented in null(4) but documented in dumpon(8). At
the very least it should be documented in null(4).

I would advocate for exposing the feature through a new kernel interface for
this purpose (or another better suited home) rather than null(4), and then
removing (perhaps in time) the feature from null(4).

--=20
You are receiving this mail because:
You are the assignee for the bug.=