> 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/precomputed-attacks/pyrit-cracking-against-a-rainbow-table.md).

# 使用彩虹表进行 Pyrit 破解

使用 Pyrit 配合 GenPMK 数据库检查捕获到的 WPA/WPA2 握手。

该 `dic.genpmk` 该数据库也可以与 Pyrit 一起使用。

Pyrit 使用 `attack_cowpatty` 来检查预先计算的值是否与捕获到的握手匹配。ESSID 必须与创建数据库时使用的那个相同。

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2F30rqWsXEuEzuz101Z1gn%2Fimage.png?alt=media&amp;token=c4dc4342-afd2-434b-800f-bf99f59ce695" alt=""><figcaption></figcaption></figure>

### 运行查找

使用数据库、捕获文件和网络名称：

{% code overflow="wrap" %}

```bash
pyrit -e jordan -i dic.genpmk -r Capture-01.cap attack_cowpatty
```

{% endcode %}

参数如下：

* `-e jordan` 设置目标网络名称。
* `-i dic.genpmk` 导入预先计算的数据库。
* `-r Capture-01.cap` 提供捕获到的握手数据。

Pyrit 会立即找到密码。它每秒检查大约 200 万个密码。

预先计算的数据库避免了在查找时对每个候选项重新计算。

<figure><img src="https://1574813340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2F9dsDP8mhiLniqSES4NlW%2Fimage.png?alt=media&amp;token=7be487a7-b625-4f22-8e4f-e14368071e4c" 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/precomputed-attacks/pyrit-cracking-against-a-rainbow-table.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.
