[Bug 222632] Enable Capsicum for connect(2)

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Wed Sep 27 00:05:01 UTC 2017


--- Comment #5 from Shawn Webb <shawn.webb at hardenedbsd.org> ---
(In reply to Brooks Davis from comment #4)
That's essentially what I'm doing. I'm writing a non-capsicumized child process
that handles socket and file descriptor creation in addition to file system
access calls (like unlink, rename, etc.). I'm using file descriptor passing
over a socketpair between the non-Capsicumized child process and its
Capsicumized parent.

It seems, though, that CAP_CONNECT shouldn't even exist if connect(2) doesn't
support Capsicum. All of FreeBSD's official documentation leads developers like
me to believe that calling connect(2) within a capabilities enabled process is

It seems non-intuitive that I have to wrap connect(2) via the file descriptor
passing mechanism I've designed, especially with CAP_CONNECT exists.

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

More information about the freebsd-bugs mailing list