Find which running Linux applications use PKCS#11 providers, then inspect their observed calls, errors, latency and bounded metadata — without replacing the provider or changing each application's configuration.
p11scope answers "which program uses my PKCS#11 token/provider, with which
mechanisms, how fast, what errors": eBPF uprobes observe the providers already
mapped by running processes, so there is no shim to install and no restart.
Status: v0.7.1 answers "which application used which key, and how", with opt-in live key operations (
inventory --key-operations), streaming inventory events (--event-log -with--event-interval), and a published observer image (ghcr.io/mingulov/p11scope:latest). Read the known limitations before relying on a capture; CHANGELOG.md records what this release was qualified on.
Get the bundles from the Releases page (observer tarball, optional discovery helpers, DEB/RPM packages, source export). The 0.7.1 files are listed under the v0.7.1 release. For example, install v0.7.1 after verifying its checksum:
download_dir=$(mktemp -d /var/tmp/p11scope-install.XXXXXX)
cd "$download_dir"
curl -fLO https://github.com/mingulov/p11scope/releases/download/v0.7.1/p11scope-0.7.1-x86_64-linux-musl.tar.gz
curl -fLO https://github.com/mingulov/p11scope/releases/download/v0.7.1/SHA256SUMS
sha256sum --check --ignore-missing SHA256SUMS
tar -xzf p11scope-0.7.1-x86_64-linux-musl.tar.gz
sudo install -m 0755 p11scope-0.7.1-x86_64-linux-musl/p11scope /usr/local/bin/p11scope
p11scope --version
sudo p11scope doctor(doctor loads its BPF preflight on every run, so expect about 10 s
with no interim output; that is normal.)
System packages, the discovery helper and local builds are in Install.
To check a download before installing, see Verify a download.
Container: the release publishes ghcr.io/mingulov/p11scope:latest
(:0.7.1 pins the exact version).
Run doctor through it (privileges):
docker run --rm --pid=host --cap-drop ALL --cap-add BPF --cap-add PERFMON --cap-add CHECKPOINT_RESTORE --cap-add SYS_PTRACE --cap-add DAC_READ_SEARCH -v /sys/fs/cgroup:/sys/fs/cgroup:ro ghcr.io/mingulov/p11scope:latest doctorOn Ubuntu and other AppArmor hosts, add --security-opt apparmor=unconfined: Docker confines every container with
docker-default, which blocks reading other processes, so without the
flag the run sees almost nothing. Docker 24+ needs no seccomp flag;
older engines use the vendored
seccomp profile. The demo
pages have the full copy-paste
commands, the hardened profile alternative, and the measured numbers.
Alternative: --cap-add SYS_ADMIN --cap-add SYS_PTRACE --cap-add DAC_READ_SEARCH in place of the --cap-drop ALL and five
--cap-add flags above.
CAP_SYS_ADMIN grants very broad power — close to full root (mounts,
namespaces, many kernel admin operations) — so use it only when
needed. What it adds for p11scope is file learning (fanotify): it
catches a short-lived process's first load of a new provider file;
without it that case is a named gap in the report. On Docker older
than 24, whose default seccomp allows bpf() only with
CAP_SYS_ADMIN, it is also the way to run without the seccomp file.
# Check this machine can capture.
sudo p11scope doctor
# List which programs use PKCS#11 providers right now.
sudo p11scope inventory --system --duration 15s
# Watch one program in detail (use a PID from the inventory above, or `pidof <name>`).
sudo p11scope profile --pid <PID> --duration 30sNew here? Work through the Quickstart: it sets up a throwaway SoftHSM token and runs your first observed workload in a few minutes.
One-shot tools (a single pkcs11-tool call) under --system are
caught from their second run inside one capture: the provider file is
learned from the kernel, listed with the program that first loaded it,
and attached so later runs are counted. The first use itself stays a
named miss — wrap such tools in sudo p11scope run --user $USER -- <tool> (or pass --prearm-module PATH) when first-run coverage
matters.
doctor reports host readiness (real output, v0.7.1 on Ubuntu 26.04):
Doctor: requested-lane checks passed.
verdict: capture available
Next: choose --pid <PID> or --cgroup <PATH> to assess a target scope.
run with -v for details
Rows vary by host; run with -v for details lists every check.
<PID> is the program you picked. Add -o report.json to also save the full machine-readable report next to the terminal summary. If a command refuses instead of capturing, see troubleshooting.
Text is concise by default; -v shows full detail. Complete output: --json on inspect/inventory (incl. inventory diff, cbom); -o FILE on profile/run/inventory; trace streams text to -o FILE or -o -; inventory streams --event-log; doctor is text-only.
- Linux x86-64 with BTF (
/sys/kernel/btf/vmlinux). - Kernel 6.6+ (or a working backport) for full live-capture support.
- Root, or the documented minimal capability set (
CAP_BPF,CAP_CHECKPOINT_RESTORE,CAP_DAC_READ_SEARCH,CAP_PERFMON,CAP_SYS_PTRACE; noCAP_SYS_ADMINon the default lane).
p11scope sends no telemetry and makes no network connections.
- Install — bundles, packages, helper, building from source.
- Operator's guide — running captures and reading the evidence.
- Overview — what it observes, honest claims, tested targets.
- Troubleshooting — refusals and empty captures.
- Kubernetes — node DaemonSet observer.
- Why not just pkcs11-spy? — shims compared.
- Privacy allowlists (v2) — captured fields.
- Profile schema v3 — report format.
- Known limitations — what this release does not do.
- Changelog — per-release changes and qualification.
- Releases — downloads and notes.
Copyright (C) 2026 Denis Mingulov [email protected]. See COPYRIGHT.
Public license: GPL-3.0-or-later — see LICENSE.
BPF sources: GPL-2.0-only — see
LICENSES/GPL-2.0-only.txt.
Shared BPF/userspace definitions (crates/ebpf-common): GPL-2.0-or-later — see
LICENSES/GPL-2.0-or-later.txt. This crate is
compiled into both the BPF object the kernel loads (used there under GPL-2.0)
and the observer (used there under GPL-3.0).
Per-file SPDX tags (GPL-3.0-or-later for userspace, docs, and scripts;
GPL-2.0-only for BPF programs; GPL-2.0-or-later for crates/ebpf-common)
remove any ambiguity.
Contributions require a CLA granting broad sublicensing/relicensing rights; see CONTRIBUTING.md.