> 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/reconnaissance-and-capture/wireless-sniffing-techniques.md).

# 无线嗅探技巧

了解无线流量分析能揭示什么，以及加密如何限制暴露面。

无线流量嗅探会收集数据包进行分析。它有助于评估网络暴露了哪些信息。

{% hint style="warning" %}
在已记录的授权和范围内捕获流量。
{% endhint %}

### 流量分析可以揭示什么

未加密的流量可能暴露敏感信息。根据协议不同，观察者可能识别出：

* DNS 请求以及设备解析的域名。
* 用户访问的网站或服务。
* 图像、文件以及其他未加密内容。
* HTTP 表单提交和 POST 请求数据。
* 设备地址、网络名称和连接时间。
* 协议、端口、数据包大小和通信模式。

流量元数据仍然可以揭示活动模式。即使有效负载已加密，这一点依然成立。

### 加密限制可见性

HTTPS 会在传输过程中加密页面内容、凭据、图像和表单数据。它可防止直接读取受保护的请求内容。

加密 DNS 也会降低域名可见性。示例包括通过 HTTPS 的 DNS 和通过 TLS 的 DNS。

加密并不会隐藏所有细节。观察者仍可能看到目标地址、连接时间和流量大小。

### 防御性检查

使用数据包分析确认敏感服务使用了加密。

* 检查 Web 应用是否将 HTTP 流量重定向到 HTTPS。
* 确认登录表单绝不会通过 HTTP 发送凭据。
* 检查 DNS 设置和加密 DNS 支持。
* 识别网络中意外出现的明文协议。

记录暴露的数据、受影响的设备以及所涉及的协议。这有助于更容易地确定修复优先级。

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2FRFmZ7lH2t8InzGwtlkIZ%2Fimage.png?alt=media&amp;token=26821ac2-eb44-4f5b-a81a-0747059d50f3" alt=""><figcaption></figcaption></figure>


---

# 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/reconnaissance-and-capture/wireless-sniffing-techniques.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.
