> 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/fundamentals/what-is-a-handshake.md).
# What Is a Handshake?
Understand the WPA/WPA2 exchange and capture it during an authorized assessment.
A WPA/WPA2 handshake is the authentication exchange between a client and an access point. It occurs when the client connects or reconnects to the network.
The capture contains cryptographic values. It does not contain the password in plain text.
### Passive capture
During an assessment, wait for a natural reconnection. Keep the capture limited to the in-scope access point and channel.
### Active capture
A scoped test network can use an active technique to trigger a client reconnection. A targeted deauthentication test is one option when the access point and client are explicitly in scope.
### Later validation
Preserve the capture file and record its source, date, and scope. Then validate that the exchange is complete before continuing the authorized analysis.
{% hint style="info" %}
A handshake capture proves an authentication event. It does not prove password strength by itself.
{% 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/fundamentals/what-is-a-handshake.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.
