> 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/ru/hacking-wifi/wpa-wpa2-psk-network-attacks/precomputed-attacks/cracking-with-pyrit.md).
# Взлом с помощью Pyrit
Сравните скорость восстановления паролей WPA/WPA2 с помощью Pyrit и Hashcat.
Этот тест сравнивает производительность восстановления пароля с Pyrit и Hashcat. Оба инструмента используют один и тот же захват и один и тот же список паролей.
Целевой пароль — `92212345`.
### Извлеките хэш
{% code overflow="wrap" %}
```bash
wpapcap2john Capture-01.cap > Hash
```
{% endcode %}
Просмотрите извлечённые хэши:
{% code overflow="wrap" %}
```bash
cat Hash
```
{% endcode %}
### Создайте список паролей
Создайте `passwords.txt` файл с 100 000 кандидатами:
{% code overflow="wrap" %}
```bash
seq 92162345 92262345 > passwords.txt
```
{% endcode %}
### Проверка с John
Запустите восстановление:
{% code overflow="wrap" %}
```bash
john --format=wpapsk -w=passwords.txt Hash
```
{% endcode %}
Это занимает около 1 минуты 40 секунд.
### Проверка с Pyrit
Затем определите имя точки доступа. Это `Jordan`.
{% code overflow="wrap" %}
```bash
echo -n "$(cat hash.22000 | cut -d'*' -f6)" | xxd -r -p
```
{% endcode %}
Pyrit использует `attack_passthrough` для вычисления `PMK = PBKDF2(ESSID, password)` для каждого `passwords.txt` записи. Он сравнивает каждый результат с рукопожатием.
{% code overflow="wrap" %}
```bash
pyrit -r Capture-01.cap -e Jordan -i passwords.txt attack_passthrough
```
{% endcode %}
Это занимает 1 мин 29 секунд.
### Сравнение с Hashcat
Аналогичный рабочий процесс Hashcat начинается с преобразования захвата:
```bash
hcxpcapngtool -o hash.22000 Capture-01.cap
```
Затем запустите восстановление:
{% code overflow="wrap" %}
```bash
hashcat -m 22000 hash.22000 passwords.txt
```
{% endcode %}
Это занимает около 1 минуты 30 секунд.
---
# 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/ru/hacking-wifi/wpa-wpa2-psk-network-attacks/precomputed-attacks/cracking-with-pyrit.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.
