Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 02 Oct 2017 09:00:58 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-bugs@FreeBSD.org
Subject:   [Bug 222632] Enable Capsicum for connect(2)
Message-ID:  <bug-222632-8-PO2CjMdgkw@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/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D222632

Ed Maste <emaste@freebsd.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |emaste@freebsd.org

--- Comment #11 from Ed Maste <emaste@freebsd.org> ---
(In reply to Shawn Webb from comment #10)
> However, long-term, we should figure out how to be able to call connect(2=
) in capmode.

As a kernel interface that provides access to global namespaces connect(2)
cannot be called in capability mode. I looked at the capsicum(4) man page a=
gain
now, and it certainly seems we need a more thorough explanation in there. T=
his
statement alludes to connect(2) not being available:

> capability mode
>   A process mode, entered by invoking cap_enter(2), in which access
>   to global OS namespaces (such as the file system and PID names=E2=80=90
>   paces) is restricted

but it's certainly not a sufficient guide for refactoring existing applicat=
ions
for applying Capsicum.

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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-222632-8-PO2CjMdgkw>