> 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-cracking-against-a-rainbow-table.md).
# Pyrit-Cracking gegen eine Rainbow Table
Pyrit mit einer GenPMK-Datenbank verwenden, um einen erfassten WPA/WPA2-Handshake zu prüfen.
Das `dic.genpmk` Die Datenbank kann auch mit Pyrit verwendet werden.
Pyrit verwendet `attack_cowpatty` um die vorab berechneten Werte mit dem mitgeschnittenen Handshake zu vergleichen. Die ESSID muss mit der beim Erstellen der Datenbank verwendeten übereinstimmen.
### Führe die Suche aus
Verwende die Datenbank, den Mitschnitt und den Netzwerknamen:
{% code overflow="wrap" %}
```bash
pyrit -e jordan -i dic.genpmk -r Capture-01.cap attack_cowpatty
```
{% endcode %}
Die Parameter sind:
* `-e jordan` legt den Ziel-Netzwerknamen fest.
* `-i dic.genpmk` importiert die vorab berechnete Datenbank.
* `-r Capture-01.cap` liefert den mitgeschnittenen Handshake.
Pyrit findet das Passwort sofort. Es prüft etwa 2 Millionen Passwörter pro Sekunde.
Die vorab berechnete Datenbank vermeidet es, jeden Kandidaten während der Suche neu zu berechnen.
---
# 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-cracking-against-a-rainbow-table.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.
