> 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/es/hacking-wifi/wpa-wpa2-psk-network-attacks/reconnaissance-and-capture/passive-exploitation-techniques.md).
# Técnicas de explotación pasiva
Observa el tráfico WiFi autorizado para capturar handshakes WPA/WPA2 sin interrumpir a los clientes.
Una técnica pasiva observa la actividad de la red sin obligar a un cliente a desconectarse. Puede capturar un handshake de WPA/WPA2 cuando un cliente dentro del alcance se conecta o se reconecta.
### Captura pasiva
Durante una evaluación, supervise el punto de acceso y el canal aprobados. Espere una conexión o reconexión natural del cliente.
### Cuando aparece un handshake
Un handshake puede aparecer cuando un cliente se une a la red. También puede aparecer cuando un cliente pierde brevemente la señal y se reconecta.
Por ejemplo, en una red de prueba que simula una cafetería, espere a que un cliente aprobado se reconecte. Este enfoque puede requerir bastante tiempo cuando la actividad de la red es baja.
{% hint style="info" %}
La observación pasiva evita interrumpir a los clientes. No garantiza un handshake dentro de un plazo fijo.
{% 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/es/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.
