From owner-freebsd-bugs@freebsd.org  Sat Sep 16 13:18:33 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 43A99E160BD
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Sat, 16 Sep 2017 13:18:33 +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 31EE575D69
 for <freebsd-bugs@FreeBSD.org>; Sat, 16 Sep 2017 13:18:33 +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 v8GDIW0s037977
 for <freebsd-bugs@FreeBSD.org>; Sat, 16 Sep 2017 13:18:33 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 222258] renameat(2) capability error with absolute path names
 outside of a sandbox
Date: Sat, 16 Sep 2017 13:18:33 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 11.0-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: jilles@FreeBSD.org
X-Bugzilla-Status: Open
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: bug_status cc
Message-ID: <bug-222258-8-be7XdbTZx6@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-222258-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-222258-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: Sat, 16 Sep 2017 13:18:33 -0000

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

Jilles Tjoelker <jilles@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|New                         |Open
                 CC|                            |jilles@FreeBSD.org

--- Comment #6 from Jilles Tjoelker <jilles@FreeBSD.org> ---
(In reply to Ed Maste from comment #5)
The block of code checking for CAP_UNLINKAT should not apply when an absolu=
te
path was originally passed to the system call. This is needed to maintain
POSIX's requirement that renameat() be equivalent to rename() unless either=
 old
or new specifies a relative path. I don't immediately know how to code this
best.

The patch from Conrad Meyer seems wrong since capabilities are supposed to =
be
enforced for all processes, not only ones in capability mode. This feature =
may
be useful when passing file descriptors to a process with a lower privilege
level.

In any case, this seems a valid bug.

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