> 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/hacking-wifi/wpa-wpa2-psk-network-attacks/traffic-manipulation/airdecap-packet-decryption.md).
# Airdecap Packet Decryption
Decrypt an authorized WiFi capture with Airdecap-ng and inspect HTTP traffic.
An encrypted WiFi capture cannot be inspected directly. For example, filtering for HTTP traffic before decrypting the capture does not return results:
{% code overflow="wrap" %}
```bash
tshark -r Capture-01.cap -Y "http"
```
{% endcode %}
no funcionaria
### Decrypt the WiFi capture
Airdecap-ng decrypts the WiFi layer when you provide the correct network name and passphrase. The resulting capture can then be inspected.
An incorrect passphrase does not decrypt the traffic:
{% code overflow="wrap" %}
```bash
airdecap-ng -e jordan -p PasswordIncorrect1234 capture_jordan2-01.cap
```
{% endcode %}
Use the correct passphrase to decrypt the capture:
{% code overflow="wrap" %}
```bash
airdecap-ng -e jordan -p 92212345 capture_jordan2-01.cap
```
{% endcode %}
### Inspect HTTP requests
Airdecap-ng creates a decrypted capture file. Filter it for HTTP POST requests:
{% code overflow="wrap" %}
```bash
tshark -r capture_jordan-01-dec.cap -Y "http.request.method==POST" -Tjson 2>/dev/null
```
{% endcode %}
The output shows submitted form data when the application uses unencrypted HTTP.
To inspect submitted HTTP fields in more detail:
{% code overflow="wrap" %}
```bash
tshark -r capture_jordan-01-dec.cap -Y "http.request.method==POST" -Tjson -e http.file_data 2>/dev/null
```
{% endcode %}
WiFi decryption does not decrypt HTTPS. HTTPS request bodies remain protected.
---
# 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/hacking-wifi/wpa-wpa2-psk-network-attacks/traffic-manipulation/airdecap-packet-decryption.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.
