From owner-freebsd-bugs@freebsd.org  Sun Mar 19 19:18:19 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 53391D13E9A
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Sun, 19 Mar 2017 19:18:19 +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 42CF618D
 for <freebsd-bugs@FreeBSD.org>; Sun, 19 Mar 2017 19:18:19 +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 v2JJIJrg030675
 for <freebsd-bugs@FreeBSD.org>; Sun, 19 Mar 2017 19:18:19 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 217924] dhclient: Fails to fork into the background with
 kern.trap_enotcap=1
Date: Sun, 19 Mar 2017 19:18:19 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: bin
X-Bugzilla-Version: CURRENT
X-Bugzilla-Keywords: patch
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: tobik@freebsd.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 keywords bug_severity priority component assigned_to
 reporter attachments.created
Message-ID: <bug-217924-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: Sun, 19 Mar 2017 19:18:19 -0000

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

            Bug ID: 217924
           Summary: dhclient: Fails to fork into the background with
                    kern.trap_enotcap=3D1
           Product: Base System
           Version: CURRENT
          Hardware: Any
                OS: Any
            Status: New
          Keywords: patch
          Severity: Affects Only Me
          Priority: ---
         Component: bin
          Assignee: freebsd-bugs@FreeBSD.org
          Reporter: tobik@freebsd.org

Created attachment 180966
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D180966&action=
=3Dedit
dhclient.diff

With the sysctl kern.trap_enotcap=3D1, dhclient fails to fork into the
background and dies. truss excerpt:

4933: <new process>
4933: setsid()                                  =3D 4933 (0x1345)
4933: sigaction(SIGHUP,{ SIG_DFL 0x0 ss_t },0x0) =3D 0 (0x0)
4933: open("/dev/null",O_RDWR,00)               ERR#94 'Not permitted in
capability mode'
4933: SIGNAL 5 (SIGTRAP)

There is an older comment in dhclient.c that says that it is expected
that daemon(3) will fail to open /dev/null in a chroot.  The is doubly
true when in capability mode.  dhclient replicates the behavior of
daemon(3) in dup'ing /dev/null (with a previously opened fd) anyway,
so why isn't noclose set too?  This way the attempt to open /dev/null
again can be avoided.

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