Pilot Keychain

Secure credential exchange with auto-expiry for Pilot Protocol agents. Use this skill when: 1. You need to share API keys, tokens, or credentials securely be...

This skill generally does what it says (shares credentials via pilotctl) but the instructions leave gaps that could leak secrets. Before installing or using it: 1) Confirm pilotctl/pilot-protocol come from a trusted source and verify whether pilotctl encrypts files in transit and at rest. 2) Ensure jq and openssl are available (they are used but not declared as required binaries in metadata). 3) Hardening recommendations: use mktemp for temporary files, set restrictive permissions (umask/chmod 600) on any credential files, avoid writing secrets to /tmp if other users exist on the host, avoid printing secrets to stdout (do not expose to shells/logs), and add reliable cleanup/traps to remove files on failure. 4) Test in an isolated environment first. If you need strong guarantees about non-persistence, prefer an approach that streams secrets through an authenticated, encrypted channel instead of writing them to disk.

Type: OpenClaw Skill Name: pilot-keychain Version: 1.0.0 The skill facilitates credential exchange using the Pilot Protocol and the pilotctl utility. While its behavior aligns with its stated purpose, it contains security vulnerabilities, such as writing sensitive credentials to /tmp and potential shell injection risks in the 'Receive' and 'Cleanup' commands where jq output is passed directly to xargs and date without sanitization. These flaws could be exploited by a malicious peer sending crafted filenames or metadata, though no evidence of intentional malice by the author is present.