> 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/password-auditing/extracting-the-handshake-hash-with-aircrack.md).
# Extracción de un hash de handshake con Aircrack-ng
Exporta una captura de handshake WPA/WPA2 autorizada para herramientas de auditoría de contraseñas sin conexión.
### Resumen
Use este flujo de trabajo para una red que posea o para la que esté autorizado a realizar una evaluación.
Aircrack-ng exporta un handshake WPA/WPA2 capturado a un `.hccap` archivo. Este archivo contiene datos del handshake para herramientas de auditoría de contraseñas sin conexión. No revela la frase de contraseña de la red.
Confirme que la captura contiene un handshake válido antes de exportarla.
### Exportar la captura del handshake
Convertir `CAPTURE-01.cap` a un `.hccap` archivo:
{% code overflow="wrap" %}
```bash
aircrack-ng -J myCapture CAPTURE-01.cap
```
{% endcode %}
El comando crea `myCapture.hccap`.
### Crear una entrada de hash
Use `hccap2john` para convertir el archivo exportado en una entrada de hash:
{% code overflow="wrap" %}
```bash
hccap2john myCapture.hccap > hash
```
{% endcode %}
El `hash` archivo contiene el hash del handshake extraído. Úselo solo con herramientas aprobadas de auditoría de contraseñas.
### Validar la salida
Revise la salida antes de usarla:
* Confirme que la salida contiene una entrada de hash.
* Mantenga la captura y el archivo hash dentro del alcance de la evaluación.
* Trate el hash como material de autenticación sensible.
---
# 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/password-auditing/extracting-the-handshake-hash-with-aircrack.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.
