> 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-cracking-against-a-rainbow-table.md).

# Crackeo con Pyrit contra una tabla arcoíris

Usa Pyrit con una base de datos GenPMK para comprobar un handshake WPA/WPA2 capturado.

El `dic.genpmk` también se puede usar con Pyrit.

Pyrit usa `attack_cowpatty` para comprobar los valores precalculados frente al handshake capturado. El ESSID debe coincidir con el usado al crear la base de datos.

<figure><img src="https://754079710-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2F30rqWsXEuEzuz101Z1gn%2Fimage.png?alt=media&amp;token=c4dc4342-afd2-434b-800f-bf99f59ce695" alt=""><figcaption></figcaption></figure>

### Ejecute la búsqueda

Use la base de datos, la captura y el nombre de la red:

{% code overflow="wrap" %}

```bash
pyrit -e jordan -i dic.genpmk -r Capture-01.cap attack_cowpatty
```

{% endcode %}

Los parámetros son:

* `-e jordan` establece el nombre de la red objetivo.
* `-i dic.genpmk` importa la base de datos precalculada.
* `-r Capture-01.cap` proporciona el handshake capturado.

Pyrit encuentra la contraseña inmediatamente. Comprueba unas 2 millones de contraseñas por segundo.

La base de datos precalculada evita recalcular cada candidato durante la búsqueda.

<figure><img src="https://754079710-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2F9dsDP8mhiLniqSES4NlW%2Fimage.png?alt=media&amp;token=7be487a7-b625-4f22-8e4f-e14368071e4c" alt=""><figcaption></figcaption></figure>


---

# 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-cracking-against-a-rainbow-table.md?ask=<question>&goal=<user_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.
