From owner-freebsd-bugs@freebsd.org  Wed Sep 27 13:10:54 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 D42ABE035E0
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Wed, 27 Sep 2017 13:10:54 +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 B582971E8E
 for <freebsd-bugs@FreeBSD.org>; Wed, 27 Sep 2017 13:10:54 +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 v8RDAsaM011693
 for <freebsd-bugs@FreeBSD.org>; Wed, 27 Sep 2017 13:10:54 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 222632] Enable Capsicum for connect(2)
Date: Wed, 27 Sep 2017 13:10:54 +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: CURRENT
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Many People
X-Bugzilla-Who: domagoj.stolfa@gmail.com
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: cc
Message-ID: <bug-222632-8-znumKX1agC@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-222632-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-222632-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: Wed, 27 Sep 2017 13:10:54 -0000

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

Domagoj Stolfa <domagoj.stolfa@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |domagoj.stolfa@gmail.com

--- Comment #8 from Domagoj Stolfa <domagoj.stolfa@gmail.com> ---
I've not investigated this too much, but I can see why in some sense,
connect(2) could be seen as gaining an additional capability and could have
issues. The connectat(2) system call is the one that works with PF_LOCAL
sockets, so you could use that instead for a Unix socket.

There does seem to be a discrepancy across the documentation and what is
actually implemented, as CAP_CONNECT explicitly states that connect(2) is
allowed and the check is in place in the actual implementation, but connect=
 is
not present in sys/kern/capabilities.conf, resulting in ECAPMODE.

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