> 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/password-auditing/extracting-the-handshake-hash-with-aircrack.md).

# Extraindo um Hash de Handshake com Aircrack-ng

Exporte uma captura autorizada de handshake WPA/WPA2 para ferramentas offline de auditoria de senhas.

### Visão geral

Use este fluxo de trabalho para uma rede que você possui ou está autorizado a avaliar.

O Aircrack-ng exporta um handshake WPA/WPA2 capturado para um `.hccap` arquivo. Esse arquivo contém dados do handshake para ferramentas de auditoria de senha offline. Ele não revela a frase-senha da rede.

Confirme que a captura contém um handshake válido antes de exportá-lo.

### Exportar a captura do handshake

Converter `CAPTURE-01.cap` para um `.hccap` arquivo:

{% code overflow="wrap" %}

```bash
aircrack-ng -J myCapture CAPTURE-01.cap
```

{% endcode %}

<figure><img src="https://783634792-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2FS6NFFyUStJPs9Xoc737y%2F%7B07C7C5AB-FD31-4E4F-AB28-D5B9E4C8CF32%7D.png?alt=media&amp;token=45e1bebc-fa38-4881-8a75-b3c55bb11917" alt=""><figcaption></figcaption></figure>

O comando cria `myCapture.hccap`.

### Criar uma entrada de hash

Use `hccap2john` para converter o arquivo exportado em uma entrada de hash:

{% code overflow="wrap" %}

```bash
hccap2john myCapture.hccap > hash
```

{% endcode %}

O `hash` arquivo contém o hash do handshake extraído. Use-o somente com ferramentas aprovadas de auditoria de senha.

### Validar a saída

Revise a saída antes de usá-la:

* Confirme que a saída contém uma entrada de hash.
* Mantenha a captura e o arquivo de hash dentro do escopo da avaliação.
* Trate o hash como material de autenticação sensível.

<figure><img src="https://783634792-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fo96yzfJlSxjvFfyjiPik%2F%7B1F46BB2A-B9D1-43B2-8D59-CAE04AE8A306%7D.png?alt=media&amp;token=83200e75-3f01-4855-ab2f-0930f9896f03" 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/password-auditing/extracting-the-handshake-hash-with-aircrack.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.
