> 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/reconnaissance-and-capture/passive-exploitation-techniques.md).
# Passive Exploitation Techniques
Observe authorized WiFi traffic to capture WPA/WPA2 handshakes without disrupting clients.
A passive technique observes network activity without forcing a client to disconnect. It can capture a WPA/WPA2 handshake when an in-scope client connects or reconnects.
### Passive capture
During an assessment, monitor the approved access point and channel. Wait for a natural client connection or reconnection.
### When a handshake appears
A handshake can appear when a client joins the network. It can also appear when a client briefly loses signal and reconnects.
For example, in a test network that simulates a café, wait for an approved client to reconnect. This approach can require significant time when network activity is low.
{% hint style="info" %}
Passive observation avoids disrupting clients. It does not guarantee a handshake within a fixed timeframe.
{% endhint %}
---
# 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/reconnaissance-and-capture/passive-exploitation-techniques.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.