> 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-database-attack-cracking.md).
# Quebra com Ataque ao Banco de Dados do Pyrit
Pré-compute chaves WPA/WPA2 em um banco de dados do Pyrit e teste um handshake capturado.
Os ataques de banco de dados do Pyrit pré-computam chaves antes de testar a captura. Isso torna a busca final muito rápida.
O fluxo de trabalho importa candidatos de senha, adiciona o ESSID de destino e gera os valores necessários.
### Importar candidatos de senha
Importe a lista de senhas para o banco de dados do Pyrit:
{% code overflow="wrap" %}
```bash
pyrit -i passwords.txt import_passwords
```
{% endcode %}
### Criar o ESSID
Adicione o nome da rede de destino:
{% code overflow="wrap" %}
```bash
pyrit -e jordan create_essid
```
{% endcode %}
### Pré-computar as chaves
Gere os valores do banco de dados para as senhas importadas e o ESSID:
{% code overflow="wrap" %}
```bash
pyrit batch
```
{% endcode %}
### Testar a captura
Execute o ataque ao banco de dados contra o handshake capturado:
{% code overflow="wrap" %}
```bash
pyrit -r Capture-01.cap attack_db
```
{% endcode %}
Este teste leva 0,0001 segundos. O Pyrit verifica cerca de 93 milhões de senhas por segundo.
O banco de dados pré-computado evita calcular cada senha durante a busca 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/pt-br/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.
