capable.bt(8) System Manager's Manual capable.bt(8)

# [NAME](#NAME)

capable.bt - Trace security capability checks (cap\_capable()).

# [SYNOPSIS](#SYNOPSIS)

**capable.bt**

# [DESCRIPTION](#DESCRIPTION)

This traces security capability checks in the kernel, and prints details for each call. This can be useful for general debugging, and also security enforcement: determining a white list of capabilities an application needs.

Since this uses BPF, only the root user can use this tool.

# [REQUIREMENTS](#REQUIREMENTS)

CONFIG\_BPF, bpftrace.

# [EXAMPLES](#EXAMPLES)

[Trace all capability checks system-wide:](#Trace)

\# **capable.bt**

# [FIELDS](#FIELDS)

[TIME(s)](#TIME%28s%29)

Time of capability check: HH:MM:SS.

[UID](#UID)

User ID.

[PID](#PID)

Process ID.

[COMM](#COMM)

Process name.

[CAP](#CAP)

Capability number.

[NAME](#NAME~2)

Capability name. See [capabilities(7)](/man/enterprise-packages/bpftrace/capabilities.7) for descriptions.

[AUDIT](#AUDIT)

Whether this was an audit event.

# [OVERHEAD](#OVERHEAD)

This adds low-overhead instrumentation to capability checks, which are expected to be low frequency, however, that depends on the application. Test in a lab environment before use.

# [SOURCE](#SOURCE)

This is from bpftrace.

https://github.com/bpftrace/bpftrace

Also look in the bpftrace distribution for a companion \_examples.txt file containing example usage, output, and commentary for this tool.

This is a bpftrace version of the bcc tool of the same name. The bcc tool provides options to customize the output.

https://github.com/iovisor/bcc

# [OS](#OS)

Linux

# [STABILITY](#STABILITY)

Unstable - in development.

# [AUTHOR](#AUTHOR)

Brendan Gregg

# [SEE ALSO](#SEE_ALSO)

[capabilities(7)](/man/enterprise-packages/bpftrace/capabilities.7)

2018-09-08 USER COMMANDS

---

Document: capable.bt(8) from bpftrace 0.27.1-r0 (Chainguard OS)
Source: https://github.com/bpftrace/bpftrace