> 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.md).

# WEP 网络

传统 WEP 的弱点、常见攻击模式和迁移优先级。

WEP 具有根本性的加密弱点。请将每个 WEP 网络迁移到 WPA3 或 WPA2-AES。

<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-lock-open" style="color:$primary;">:lock-open:</i></h3></td><td><h4>常见的 WEP 攻击</h4></td><td>关于最常见的 WEP 攻击模式和防御背景的说明。</td><td><a href="/zh/hacking-wifi/wep-networks/common-wep-attacks.md">常见 WEP 攻击</a></td></tr><tr><td><h3><i class="fa-user-secret" style="color:$primary;">:user-secret:</i></h3></td><td><h4>伪造身份验证攻击</h4></td><td>将测试适配器关联到一个传统的 WEP 接入点。</td><td><a href="/zh/hacking-wifi/wep-networks/fake-authentication-attack.md">伪造身份验证攻击</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/wep-networks.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.
