https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222632
Ed Maste <ema...@freebsd.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ema...@freebsd.org
--- Comment #11 from Ed Maste <ema...@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 again
now, and it certainly seems we need a more thorough explanation in there. This
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‐
> paces) is restricted
but it's certainly not a sufficient guide for refactoring existing applications
for applying Capsicum.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
