> 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/hacking-wifi/wpa-wpa2-psk-network-attacks/precomputed-attacks/cracking-with-pyrit.md).
# Cracking with Pyrit
Compare WPA/WPA2 password recovery speeds with Pyrit and Hashcat.
This test compares password recovery performance with Pyrit and Hashcat. Each tool uses the same capture and password list.
The target password is `92212345`.
### Extract the hash
{% code overflow="wrap" %}
```bash
wpapcap2john Capture-01.cap > Hash
```
{% endcode %}
View the extracted hashes:
{% code overflow="wrap" %}
```bash
cat Hash
```
{% endcode %}
### Create the password list
Create a `passwords.txt` file with 100,000 candidates:
{% code overflow="wrap" %}
```bash
seq 92162345 92262345 > passwords.txt
```
{% endcode %}
### Test with John
Run the recovery:
{% code overflow="wrap" %}
```bash
john --format=wpapsk -w=passwords.txt Hash
```
{% endcode %}
This takes about 1 minute and 40 seconds.
### Test with Pyrit
Next, identify the access point name. It is `Jordan`.
{% code overflow="wrap" %}
```bash
echo -n "$(cat hash.22000 | cut -d'*' -f6)" | xxd -r -p
```
{% endcode %}
Pyrit uses `attack_passthrough` to calculate `PMK = PBKDF2(ESSID, password)` for every `passwords.txt` entry. It compares each result with the handshake.
{% code overflow="wrap" %}
```bash
pyrit -r Capture-01.cap -e Jordan -i passwords.txt attack_passthrough
```
{% endcode %}
This takes 1 min 29 seconds.
### Compare with Hashcat
The equivalent Hashcat workflow begins by converting the capture:
```bash
hcxpcapngtool -o hash.22000 Capture-01.cap
```
Then run the recovery:
{% code overflow="wrap" %}
```bash
hashcat -m 22000 hash.22000 passwords.txt
```
{% endcode %}
This takes about 1 minute and 30 seconds.
---
# 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/hacking-wifi/wpa-wpa2-psk-network-attacks/precomputed-attacks/cracking-with-pyrit.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.
