Use PortPilot / SOURCE v3.5.7
Local state & diagnostics
Understand local storage and share useful reports without publishing your machine’s private details.
State stays with the local utility#
PortPilot uses local app preferences and user-local files under ~/.portpilot and Application Support. Sensitive POSIX files use mode 0600, app-owned private directories use 0700, and shared mutations use locks plus atomic replacement.
Alert lists, cron metadata and captured history can describe private infrastructure and activity. Permissions reduce cross-account exposure; they are not encryption or Windows ACL enforcement.
Before sharing diagnostics#
Review process paths, usernames, internal hosts, remote endpoints, cron commands and captured output. Remove credentials, tokens, account details and unrelated private activity before opening an issue.
Include your OS version, PortPilot version, the interface you used, the command or action, and whether the result was missing, stale, degraded or unexpectedly empty. A small sanitized reproduction is more useful than a full machine dump.
Packet summary capture#
The macOS app offers explicitly requested, bounded capture through the system tcpdump tool, off by default. It requires existing user capture-device access and does not install a privileged helper.
The raw 96-byte snapshots may contain initial payload bytes. PortPilot receives numeric summaries and does not save the raw capture, but a port filter is not process attribution: other processes or transit traffic can match. See the repository’s README for the capture feature’s limits.