> 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/zh/hacking-wifi/wpa-wpa2-psk-network-attacks.md).

# WPA/WPA2 PSK 网络攻击

按工作流程组织的 WPA/WPA2 PSK 无线评估指南。

本节涵盖 WPA/WPA2 PSK 网络的无线监测、抓包、中断测试、密码审计和防御性审查。

{% hint style="warning" %}
主动测试可能影响连接。在开始前请规划好恢复方案。
{% endhint %}

### WPA/WPA2 评估类别

选择一个类别以打开其分组评估指南。

<table data-view="cards" data-full-width="false" data-search="false"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h3><i class="fa-wifi" style="color:$primary;">:wifi:</i></h3></td><td><h4>基础知识</h4></td><td>监听模式、适配器设置、MAC 地址处理以及 WPA/WPA2 握手。</td><td><a href="/zh/hacking-wifi/wpa-wpa2-psk-network-attacks/fundamentals.md">基础</a></td></tr><tr><td><h3><i class="fa-magnifying-glass" style="color:$primary;">:magnifying-glass:</i></h3></td><td><h4>侦察与抓包</h4></td><td>Airodump、Bettercap、被动观察、隐藏 SSID 以及抓包证据。</td><td><a href="/zh/hacking-wifi/wpa-wpa2-psk-network-attacks/reconnaissance-and-capture.md">侦察与捕获</a></td></tr><tr><td><h3><i class="fa-boxes-stacked" style="color:$primary;">:boxes-stacked:</i></h3></td><td><h4>数据包分析</h4></td><td>探测、关联、信标、认证、取消认证和取消关联帧。</td><td><a href="/zh/hacking-wifi/wpa-wpa2-psk-network-attacks/packet-analysis.md">数据包分析</a></td></tr><tr><td><h3><i class="fa-link-slash" style="color:$primary;">:link-slash:</i></h3></td><td><h4>客户端中断测试</h4></td><td>取消认证、取消关联、信标泛洪、CTS 和 TKIP 反制测试。</td><td><a href="/zh/hacking-wifi/wpa-wpa2-psk-network-attacks/client-disruption-tests.md">客户端干扰测试</a></td></tr><tr><td><h3><i class="fa-key" style="color:$primary;">:key:</i></h3></td><td><h4>密码审计</h4></td><td>握手提取、Aircrack-ng、John、hcxdumptool 和 hcxpcaptool 工作流程。</td><td><a href="/zh/hacking-wifi/wpa-wpa2-psk-network-attacks/password-auditing.md">密码审计</a></td></tr><tr><td><h3><i class="fa-gauge-high" style="color:$primary;">:gauge-high:</i></h3></td><td><h4>预计算攻击</h4></td><td>彩虹表、GenPMK、Cowpatty、Airolib 和 Pyrit 数据库工作流程。</td><td><a href="/zh/hacking-wifi/wpa-wpa2-psk-network-attacks/precomputed-attacks.md">预计算攻击</a></td></tr><tr><td><h3><i class="fa-mask" style="color:$primary;">:mask:</i></h3></td><td><h4>邪恶双胞胎</h4></td><td>恶意 AP 设置、强制门户组件、路由、DHCP 和凭据流转风险。</td><td><a href="/zh/hacking-wifi/wpa-wpa2-psk-network-attacks/evil-twin.md">Evil Twin</a></td></tr><tr><td><h3><i class="fa-shuffle" style="color:$primary;">:shuffle:</i></h3></td><td><h4>流量操控</h4></td><td>解密抓包和 HTTP 流量操控演示。</td><td><a href="/zh/hacking-wifi/wpa-wpa2-psk-network-attacks/traffic-manipulation.md">流量操纵</a></td></tr><tr><td><h3><i class="fa-unlock-keyhole" style="color:$primary;">:unlock-keyhole:</i></h3></td><td><h4>WPS</h4></td><td>WPS 暴露情况审查、攻击路径和修复优先级。</td><td><a href="/zh/hacking-wifi/wpa-wpa2-psk-network-attacks/wps.md">WPS</a></td></tr></tbody></table>


---

# 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/zh/hacking-wifi/wpa-wpa2-psk-network-attacks.md?ask=<question>&goal=<user_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.
