From 2a87d469501a10fc536741c7d96350f8b8d95617 Mon Sep 17 00:00:00 2001 From: Diogo Cordeiro Date: Mon, 11 Nov 2019 22:17:50 +0000 Subject: [PATCH] Fix minor typo --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 69aa3aa..e6b1ad4 100644 --- a/README.md +++ b/README.md @@ -87,7 +87,7 @@ airodump-ng -c 3 --bssid 9C:5C:8E:C9:AB:C0 -w . mon0 Now we wait... Once you've captured a handshake, you should see something like `[ WPA handshake: bc:d3:c9:ef:d2:67` at the top right of the screen, just right of the current time. -If you are feeling impatient, and are comfortable using an active attack, you can force devices connected to the target network to reconnect, be sending malicious deauthentication packets at them. This often results in the capture of a 4-way handshake. See the [deauth attack section](#deauth-attack) below for info on this. +If you are feeling impatient, and are comfortable using an active attack, you can force devices connected to the target network to reconnect, by sending malicious deauthentication packets at them. This often results in the capture of a 4-way handshake. See the [deauth attack section](#deauth-attack) below for info on this. Once you've captured a handshake, press `ctrl-c` to quit `airodump-ng`. You should see a `.cap` file wherever you told `airodump-ng` to save the capture (likely called `-01.cap`). We will use this capture file to crack the network password. I like to rename this file to reflect the network name we are trying to crack: