Changeset View
Changeset View
Standalone View
Standalone View
lib/libcasper/libcasper/libcasper.3
Show All 22 Lines | |||||
.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) | .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) | ||||
.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT | .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT | ||||
.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY | .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY | ||||
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF | .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF | ||||
.\" SUCH DAMAGE. | .\" SUCH DAMAGE. | ||||
.\" | .\" | ||||
.\" $FreeBSD$ | .\" $FreeBSD$ | ||||
.\" | .\" | ||||
.Dd September 29, 2022 | .Dd January 10, 2023 | ||||
.Dt LIBCASPER 3 | .Dt LIBCASPER 3 | ||||
.Os | .Os | ||||
.Sh NAME | .Sh NAME | ||||
.Nm cap_init , | .Nm cap_init , | ||||
.Nm cap_wrap , | .Nm cap_wrap , | ||||
.Nm cap_unwrap , | .Nm cap_unwrap , | ||||
.Nm cap_sock , | .Nm cap_sock , | ||||
.Nm cap_clone , | .Nm cap_clone , | ||||
▲ Show 20 Lines • Show All 51 Lines • ▼ Show 20 Lines | |||||
the casper daemon's services via the | the casper daemon's services via the | ||||
.Fn cap_service_open | .Fn cap_service_open | ||||
function. | function. | ||||
.Pp | .Pp | ||||
The | The | ||||
.Fn cap_init | .Fn cap_init | ||||
function instantiates a capability to allow a program to access | function instantiates a capability to allow a program to access | ||||
the casper daemon. | the casper daemon. | ||||
It must be called from a single-threaded context. | |||||
imp: Currently single threaded programs, or programs that haven't yet started additional threads? I… | |||||
Not Done Inline Actions"currently" reads somewhat strangely to me too. Maybe something like "in a single-threaded context" or "before additional threads (if any) are started"? In any case like @imp I think it's better to have something here so up to you. emaste: "currently" reads somewhat strangely to me too. Maybe something like "in a single-threaded… | |||||
Done Inline Actions"single-threaded context" sounds nice. I'll use that one. asomers: "single-threaded context" sounds nice. I'll use that one. | |||||
.Pp | .Pp | ||||
The | The | ||||
.Fn cap_wrap | .Fn cap_wrap | ||||
function creates a | function creates a | ||||
.Vt cap_channel_t | .Vt cap_channel_t | ||||
based on the socket supplied in the call. | based on the socket supplied in the call. | ||||
The function is used when a capability is inherited through the | The function is used when a capability is inherited through the | ||||
.Xr execve 2 | .Xr execve 2 | ||||
▲ Show 20 Lines • Show All 195 Lines • Show Last 20 Lines |
Currently single threaded programs, or programs that haven't yet started additional threads? I suppose the former is more correct, but maybe the latter is easier to follow?
But just a suggestion... If you don't like it, I'm good with what's here.