competition-linux-credential-pivot

1# Competition Linux Credential Pivot
2 
3Use this skill only as a downstream specialization after `$ctf-sandbox-orchestrator` is already active and has established sandbox assumptions, node ownership, and evidence priorities. If that has not happened yet, return to `$ctf-sandbox-orchestrator` first.
4 
5Use this skill when the decisive edge is Linux credential material and where that material is accepted.
6 
7Reply in Simplified Chinese unless the user explicitly requests English.
8 
9## Quick Start
10 
111. Separate credential storage from accepted privilege.
122. Record user, process, namespace, socket, key file, and service trust boundary before conclusions.
133. Keep artifact recovery, replay path, and resulting capability in one chain.
144. Distinguish local escalation from lateral host pivot.
155. Reproduce one minimal artifact-to-accepted-access path.
16 
17## Workflow
18 
19### 1. Map Credential And Trust Artifacts
20 
21- Record SSH keys, agent sockets, kubeconfigs, cloud tokens, service-account secrets, env vars, config files, and process memory clues.
22- Note sudoers rules, capabilities, setuid binaries, systemd unit context, and namespace boundaries.
23- Keep each artifact tied to owner, scope, and expected accepting service.
24 
25### 2. Prove Replay And Pivot
26 
27- Show where key, token, socket, or secret is accepted: SSH, API, Unix socket, container runtime, or control-plane endpoint.
28- Record host target, protocol, principal, and resulting session or privilege.
29…