> 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/john-brute-force-network-password-recovery.md).
# Recover Network Passwords with John
Identify a hash and test it with John the Ripper.
### Overview
Use this workflow for hashes and networks you own or are authorized to assess.
John the Ripper tests an authorized WPA/WPA2 handshake hash against a wordlist. It does not recover passwords unless a matching value exists.
Create the `hash` file before continuing. See [Extracting a Handshake Hash with Aircrack-ng](/hacking-wifi/wpa-wpa2-psk-network-attacks/password-auditing/extracting-the-handshake-hash-with-aircrack.md).
### Inspect the hash
Copy the hash from the `hash` file when you need to inspect it:
{% code overflow="wrap" %}
```bash
cat hash | xclip -sel clip
```
{% endcode %}
Use HashID to identify the likely hash format:
{% code overflow="wrap" %}
```bash
hashid 'HASH_________'
```
{% endcode %}
### Run the password audit
Use the detected format when John requires one. The first command targets WPA-PSK hashes. The second lets John detect the format automatically.
{% code overflow="wrap" %}
```bash
john --format=wpapsk --wordlist=/usr/share/wordlists/rockyou.txt hash
john --wordlist=/usr/share/wordlists/rockyou.txt hash
```
{% endcode %}
Use an approved wordlist for the assessment. `rockyou.txt` is a common example.
### Review the result
If the password appears in the wordlist, John displays the recovered value:
Record the result securely. Remove temporary hashes after the assessment.
---
# 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/john-brute-force-network-password-recovery.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.
