> 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/hacking-wifi/wpa-wpa2-psk-network-attacks/password-auditing/extracting-the-handshake-hash-with-aircrack.md).
# Extracting a Handshake Hash with Aircrack-ng
Export an authorized WPA/WPA2 handshake capture for offline password-audit tooling.
### Overview
Use this workflow for a network you own or are authorized to assess.
Aircrack-ng exports a captured WPA/WPA2 handshake to an `.hccap` file. This file contains handshake data for offline password-audit tools. It does not reveal the network passphrase.
Confirm that the capture contains a valid handshake before exporting it.
### Export the handshake capture
Convert `CAPTURE-01.cap` to an `.hccap` file:
{% code overflow="wrap" %}
```bash
aircrack-ng -J myCapture CAPTURE-01.cap
```
{% endcode %}
The command creates `myCapture.hccap`.
### Create a hash entry
Use `hccap2john` to convert the exported file into a hash entry:
{% code overflow="wrap" %}
```bash
hccap2john myCapture.hccap > hash
```
{% endcode %}
The `hash` file contains the extracted handshake hash. Use it only with approved password-audit tooling.
### Validate the output
Review the output before using it:
* Confirm that the output contains a hash entry.
* Keep the capture and hash file within the assessment scope.
* Treat the hash as sensitive authentication material.
---
# 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/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.
