pixiewps (optional, required for pixiedust attack). 
Pixie dust thread (in Kali forum) & Dominique Bongard's full disclosure
More information about the Pixie Dust attack (including which APs are vulnerable) can be found in pixiewps repository,. Reaver versioning was updated to 1.6.x in order to identify the new cycle.Īll stable relases since the first beta version of reaver 1.6 can be downloaded from our Releases page. The latest revison of reaver-wps-fork-t6x community edition is the master branch from this repository. The discontinued reaver-wps-fork-t6x community edition, reaver version 1.5.3, which includes the Pixie Dust attack, is now the old-master branch from this repository. The original Reaver (version 1.0 to 1.4) can be found in google code archives. Reaver-wps-fork-t6x version 1.6.x is a community forked version which includes various bug fixes, new features and additional attack method (such as the offline Pixie Dust attack). The first version of reaver-wps (reaver 1.0) was created by Craig Heffner in 2011. When using the offline attack, if the AP is vulnerable, it may take only a matter of seconds to minutes. 
In practice, it will generally take half this time to guess the correct WPS pin and recover the passphrase. Reaver has been designed to be a robust and practical attack against Wi-Fi Protected Setup (WPS) registrar PINs in order to recover WPA/WPA2 passphrases and has been tested against a wide variety of access points and WPS implementations.ĭepending on the target's Access Point (AP), to recover the plain text WPA/WPA2 passphrase the average amount of time for the transitional online brute force method is between 4-10 hours. Reaver implements a brute force attack against Wifi Protected Setup (WPS) registrar PINs in order to recover WPA/WPA2 passphrases, as described in Brute forcing Wi-Fi Protected Setup When poor design meets poor implementation.
0 kommentar(er)
