aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorB. Watson <yalhcru@gmail.com>2022-03-14 03:18:00 -0400
committerB. Watson <yalhcru@gmail.com>2022-03-14 03:18:00 -0400
commit02d6736d69eeeb7d441289c38a481332df44a9d9 (patch)
tree55ec5d89e4d295743433e4cfb5241e779e357fc5
parent9f0a99dcdab6952a0f6cbd2264c4e3123842c0af (diff)
network/reaver: Wrap README at 72 columns.
Signed-off-by: B. Watson <yalhcru@gmail.com>
-rw-r--r--network/reaver/README18
1 files changed, 10 insertions, 8 deletions
diff --git a/network/reaver/README b/network/reaver/README
index c7d75af9effcb..10d92d96d1df2 100644
--- a/network/reaver/README
+++ b/network/reaver/README
@@ -1,11 +1,13 @@
-Reaver implements a brute force attack against Wifi Protected Setup (WPS)
-registrar PINs in order to recover WPA/WPA2 passphrases, as described in
+Reaver implements a brute force attack against Wifi Protected Setup
+(WPS) registrar PINs in order to recover WPA/WPA2 passphrases, as
+described in:
http://sviehb.files.wordpress.com/2011/12/viehboeck_wps.pdf.
-Reaver has been designed to be a robust and practical attack against WPS, and
-has been tested against a wide variety of access points and WPS
-implementations.
+Reaver has been designed to be a robust and practical attack against
+WPS, and has been tested against a wide variety of access points and
+WPS implementations.
-On average Reaver will recover the target AP's plain text WPA/WPA2 passphrase
-in 4-10 hours, depending on the AP. In practice, it will generally take half
-this time to guess the correct WPS pin and recover the passphrase.
+On average Reaver will recover the target AP's plain text WPA/WPA2
+passphrase in 4-10 hours, depending on the AP. In practice, it will
+generally take half this time to guess the correct WPS pin and recover
+the passphrase.