> 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/fr/active-directory/kerberos/as-rep-roasting-with-wireshark.md).
# AS-REP Roasting avec Wireshark
Notes de sécurité Active Directory pour AS-REP Roasting avec Wireshark, couvrant l'énumération, Kerberos, les identifiants, l'abus des ACL, le mouvement latéral, le flux de travail d'exploitation et les étapes de validation.
### Observation manuelle
Dans le laboratoire, nous pouvons capturer le trafic avec Wireshark lors d'une tentative d'authentification.
Nous observons en particulier :
```bash
AS-REQ
AS-REP
```
Dans le paquet Kerberos, nous pouvons analyser :
```bash
padata
padata-value
chiffrement
sel
```
Ces valeurs peuvent être utilisées pour reconstruire un hash dans un format compatible avec John ou Hashcat.
### Format Hashcat 19900
Pour certains cas liés à la pré-authentification Kerberos, Hashcat peut utiliser le mode :
```
19900
```
{% embed url="" %}
Exemple de structure :
```
$krb5pa$18$user$DOMAIN$SALT$CIPHER
```
Exemple adapté au laboratoire :
{% code overflow="wrap" %}
```bash
$krb5pa$18$Administrador$WHOAMI.LOCAL$WIN-D4TRD7S7IHPAdministrador$96c289009b05181bfd32062962740b1b1ce5f74eb12e0266cde74e81094661addab08c0c1a178882c91a0ed89ae4e0e68d2820b9cce69770
```
{% endcode %}
Ensuite, nous pouvons exécuter 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/fr/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)