> 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/hacking-wifi/wpa-wpa2-psk-network-attacks/precomputed-attacks/pyrit-database-attack-cracking.md).
# Pyrit-Datenbankangriff-Cracking
WPA/WPA2-Schlüssel in einer Pyrit-Datenbank vorkalkulieren und einen erfassten Handshake testen.
Pyrit-Datenbankangriffe berechnen Schlüssel vorab, bevor der Mitschnitt getestet wird. Dadurch ist die abschließende Suche sehr schnell.
Der Workflow importiert Passwortkandidaten, fügt die Ziel-ESSID hinzu und generiert die erforderlichen Werte.
### Passwortkandidaten importieren
Importieren Sie die Passwortliste in die Pyrit-Datenbank:
{% code overflow="wrap" %}
```bash
pyrit -i passwords.txt import_passwords
```
{% endcode %}
### Die ESSID erstellen
Fügen Sie den Namen des Zielnetzwerks hinzu:
{% code overflow="wrap" %}
```bash
pyrit -e jordan create_essid
```
{% endcode %}
### Die Schlüssel vorab berechnen
Generieren Sie die Datenbankwerte für die importierten Passwörter und die ESSID:
{% code overflow="wrap" %}
```bash
pyrit batch
```
{% endcode %}
### Den Mitschnitt testen
Führen Sie den Datenbankangriff gegen den aufgezeichneten Handshake aus:
{% code overflow="wrap" %}
```bash
pyrit -r Capture-01.cap attack_db
```
{% endcode %}
Dieser Test dauert 0,0001 Sekunden. Pyrit prüft etwa 93 Millionen Passwörter pro Sekunde.
Die vorab berechnete Datenbank vermeidet die Berechnung jedes einzelnen Passworts während der abschließenden Suche.
---
# 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/hacking-wifi/wpa-wpa2-psk-network-attacks/precomputed-attacks/pyrit-database-attack-cracking.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.
