Add Kerberos trace support for forged tickets - #21691
Conversation
|
Thanks for your pull request! As part of our landing process, we manually verify that all modules work as expected. We've added the |
|
Took this for a spin in an AD lab (Server 2022 DC, real domain SID) since it's carrying Forged a golden ticket for
|
|
Additional test pipeline started ⌛ |
|
Slice summary:
Note: build results only accessible to maintainers. |
|
The four red slices look like the same thing that hit my Phase 3 PR (#21608) last week rather than anything in this change. This branch was cut from master on 2026-07-20, and #21711 landed on 2026-07-24, so the On #21608 the slices went from all four red to all four green after a rebase onto current master, with no code change at all. The diff against master was byte-identical before and after, so the base was the only variable. That is what makes me fairly confident it is the same cause here. So a rebase onto master should clear it. Unrelated to the CI, the lab run I posted above still stands. All four forge actions render correctly. |
|
Looks great @eve0805, thanks for the PR. Would you be able rebase this PR on top of the latest master? There was a regression which is currently causing the additional Jenkins tests to fail at the moment. Once you rebase I'll rerun those tests and they should pass. Thank you. Also as for @Pushpenderrathore's comment I think it makes sense for Testing |
d8e1ee9 to
d183fc5
Compare
Thanks @jheysel-r7! |
|
Had another look, this one looks separate from the Jenkins slices I mentioned earlier. Only one job really failed, the five "cancelled" are just fail-fast siblings. The real one is Failed again on the rerun, so not flake, and nowhere near this diff. This appears to be a regression already present on master. The rebase landed on Since Verify runs on the merge ref, GitHub has already recalculated it ( @jheysel-r7 the Jenkins results above predate the rebase, so they haven't hit |
|
Additional test pipeline started ⌛ |
|
Slice summary:
Note: build results only accessible to maintainers. |
d183fc5 to
25e95e9
Compare
Summary
This adds
KerberosTicketTracesupport to theauxiliary/admin/kerberos/forge_ticketmodule.The forged credential cache is rendered using the existing offline Kerberos ticket trace path introduced in #21638. This keeps forged-ticket output consistent with live Kerberos credential tracing and offline artifact inspection.
The following actions are supported:
FORGE_SILVER, rendered asFORGE_SILVER TGSFORGE_GOLDEN, rendered asFORGE_GOLDEN TGTFORGE_DIAMOND, rendering the final modified TGTFORGE_SAPPHIRE, rendering the final modified TGTTrace modes
The existing
KerberosTicketTracemodes are supported:off: preserves the existing behavior and does not print trace output.metadata: prints high-level credential metadata without ticket cipher or key material.ticket: prints the credential and encrypted ticket without using the forging key to decrypt the ticket.full: uses the available NTHASH or AES key to decrypt and display the forged ticket and PAC.The trace header includes the forge action and ticket type, for example: