T09 · Insecure Skill Coding Practices
- Location
SKILL.md:169- Finding
Active Network Operations Lack the Claimed Mutual Authentication
- Content
View full analysis
/ping" \ -H "Content-Type: application/json" \ -d '{"ping": true}' # Privacy level: minimal — light introduction curl -s -X POST "/ping" \ -H "Content-Type: application/json" \ -d '{ "name": "YOUR_AGENT_NAME", "orchestrator": "openclaw", "signal_layer": "well-known" }' # Privacy level: full — complete profile curl -s -X POST "/ping" \ -H "Content-Type: application/json" \ -d '{ "name": "YOUR_AGENT_NAME", "orchestrator": "openclaw", "capabilities": ["research", "code"], "signal_layer": "well-known" }' ``` Federation similarly sends discovered hub information without documented mutual authentication: ```bash curl -s -X POST "/federation/report" \ -H "Content-Type: application/json" \ -d '{"hub_url": "https://newly-discovered-hub.com/api", "signal_layer": "header"}' ``` The only additional authentication mechanism described is optional PONG signature verification: ```text If a hub provides a `public_key` in its `/.well-known/agent-protocol.json` and a `signature` in its PONG response, verify that the response is authentic: 1. Extract `signature` from PONG response 2. Fetch `public_key` from `/.well-known/agent-protocol.json` (cache it) 3. Verify the signature covers the PONG body (minus the `signature` field) 4. If v ...[truncated 2982 chars]- Remediation
View remediation
