Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
zhaoxuya520/competition-kerberos-delegationActive Directory and Windows

competition-kerberos-delegation

⁨Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for Kerberos delegation, SPN trust edges, S4U abuse, RBCD, constrained or unconstrained delegation, and service-ticket acceptance. Use when the user asks about constrained delegation, unconstrained delegation, RBCD, S4U, SP⁩

v2026.9.22-cab634b3 installs+3 in 7 days44.8K StarsMITsynced 2 hours ago

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install zhaoxuya520/competition-kerberos-delegation

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
hxGAfK6R20…PP/wmjAQ==The CLI checks the SHA-256 and the signature before it writes a file.
Packagefc15b4ae…325ab26f
fc15b4aef27a…ed7c325ab26f3 files · ⁦1.7 KB⁩
ScanLowno findings
The scan found nothing to flag in this version.See the full scan
Sourcegithub.com/zhaoxuya520/reverse-skill/tree/main/CTF-Sandbox-Orchestrator/competition-kerberos-delegation@cab634b

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 not "is there Kerberos here," but which delegation edge exists, which ticket is being minted, and which service really accepts it.

Reply in Simplified Chinese unless the user explicitly requests English.

Quick Start

  1. Write the trust chain first: principal -> delegation edge -> ticket type -> target SPN -> accepting service -> resulting privilege.
  2. Separate ticket possession from accepted privilege.
  3. Keep SPNs, delegation mode, PAC/group data, encryption type, and service acceptance in one compact evidence block.
  4. Reproduce one minimal delegation chain before broadening into variants.
  5. Tie every privilege claim to a specific accepted ticket or service-side effect.

Workflow

1. Identify The Delegation Edge

  • Determine whether the path is constrained delegation, unconstrained delegation, resource-based constrained delegation, protocol transition, or another trust edge.
  • Inspect SPNs, ACLs, service accounts, SIDHistory, certificate templates, and replication rights only when they affect the active path.

2. Trace Ticket Minting And Acceptance

  • Record TGT/TGS type, S4U steps when relevant, delegation flags, PAC or group data, encryption type, cache location, and target SPN.
  • Prove which service actually accepts the ticket and what capability appears after acceptance.

3. Report The Effective Edge

  • Compress the chain into one replayable path, not a vague "domain compromise" statement.
  • Separate candidate edges from the edge that really lands privilege.

Read This Reference

  • Load references/kerberos-delegation.md for the delegation checklist, ticket fields to preserve, and common proof mistakes.

What To Preserve

  • SPN, ticket type, delegation mode, PAC/group data, encryption type, cache location, accepting service
  • Service-side logs, event IDs, logon session changes, or group changes proving effective privilege
  • The exact trust edge that makes the ticket replayable

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesNoNo
Runs shell commandsNoNo
Uses the networkNoNo
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

The scan found nothing to flag in this version.

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v2026.9.22-cab634bNov 13, 2026cab634bfc15b4aeSigned–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login