OCMAP Pairing Auth

Implement one-time pairing-code authentication between an OpenClaw gateway and a desktop or remote client such as OCMAP. Use when adding or updating pairing....

This is a documentation/design-only skill that appears internally consistent. Before implementing or shipping code based on these docs: (1) confirm the skill source and trustworthiness if you obtained it externally; (2) enforce the short TTLs and single-use semantics for codes/bootstrap tokens; (3) ensure bootstrap tokens are short-lived and limited in scope, and that long-lived trusted-device tokens are stored only in backend/main process secure storage (OS keychain or encrypted app storage) and never exposed to UI renderers or logs; (4) add rate limiting, atomic marking of used codes, and feature-flag gating as suggested; and (5) run the recommended test matrix to verify there is no accidental token leakage or handshake bypass. If you plan to install code (not present here), review that code for network endpoints, storage locations, and any unexpected credential usage.

Type: OpenClaw Skill Name: ocmap-pairing-auth Version: 1.1.0 The bundle contains architectural specifications and instructions for implementing a standard one-time pairing-code authentication system between an OpenClaw gateway and a desktop client (OCMAP). The documentation (SKILL.md, protocol.md) outlines a secure cryptographic handshake using ed25519 signatures, short-lived bootstrap tokens, and single-use codes. It explicitly emphasizes security best practices, such as rate-limiting, avoiding insecure storage like localStorage, and adhering to existing 'connect-first' rules, with no indicators of malicious intent or data exfiltration.