> 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/pt-br/hacking-wifi/wpa-wpa2-psk-network-attacks/precomputed-attacks/pyrit-cracking-against-a-rainbow-table.md).

# Quebra com Pyrit Contra uma Tabela Rainbow

Use o Pyrit com um banco de dados GenPMK para verificar um handshake WPA/WPA2 capturado.

O `dic.genpmk` o banco de dados também pode ser usado com o Pyrit.

O Pyrit usa `attack_cowpatty` para verificar os valores pré-computados em relação ao handshake capturado. O ESSID deve corresponder ao usado ao criar o banco de dados.

<figure><img src="https://783634792-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>

### Execute a busca

Use o banco de dados, a captura e o nome da rede:

{% code overflow="wrap" %}

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

{% endcode %}

Os parâmetros são:

* `-e jordan` define o nome da rede de destino.
* `-i dic.genpmk` importa o banco de dados pré-computado.
* `-r Capture-01.cap` fornece o handshake capturado.

O Pyrit encontra a senha imediatamente. Ele verifica cerca de 2 milhões de senhas por segundo.

O banco de dados pré-computado evita recalcular cada candidato durante a busca.

<figure><img src="https://783634792-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/pt-br/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.
