competition-relay-coercion-chain

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Chinese

Use 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.

Use this skill when the hard part is proving the full chain from forced authentication to a service that actually accepts the relayed identity.

Reply in Simplified Chinese unless the user explicitly requests English.

仅在

$ctf-sandbox-orchestrator

已激活并建立了沙箱假设、节点所有权和证据优先级后，才可将此技能作为下游专属技能使用。如果还未满足上述条件，请先回到

$ctf-sandbox-orchestrator

流程。

当核心难点是证明从强制身份认证到实际接受中继身份的服务的完整链路时，使用此技能。

除非用户明确要求使用英文，否则请用简体中文回复。

Split the chain into coercion source, captured auth, relay target, acceptance point, and resulting effect.
Record transport, protocol, and service identity at each hop.
Separate forced-auth generation from relay success and from downstream privilege.
Keep coercion trigger, relay transcript, and accepting service in one evidence chain.
Reproduce the smallest coercion-to-acceptance path that proves the decisive edge.

Identify the service, RPC, file path, printer path, WebDAV edge, or protocol trigger that forces authentication.
Record source host, coerced principal, transport, and any environmental preconditions.
Keep one compact note of exactly what causes the auth to leave the source.

Record where the authentication lands, how it is forwarded, and which protocol or service consumes it.
Distinguish capture-only, replay-only, and actual relay acceptance.
Keep service name, target host, protocol, relay transcript, and acceptance response tied together.

Compress the result to the smallest sequence: coercion trigger -> relayed auth -> accepted service -> resulting privilege or artifact.
State clearly whether the decisive weakness lives in the coercion source, the relay target, signing settings, or the accepted downstream service.
If the path ultimately becomes a certificate-enrollment issue or a pure Kerberos delegation edge, hand off to the tighter specialized skill.

Load
```
references/relay-coercion-chain.md
```
for the coercion checklist, relay checklist, and evidence packaging.

Coercion trigger details, source host, coerced identity, target host, accepting service, and resulting effect
Relay transcripts, error or acceptance responses, and the exact protocol used at each hop
The smallest replayable coercion-to-acceptance sequence