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. by Stefan Viehboeck. 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.
Depending 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. In practice, it will
generally take half this time to guess the correct WPS pin and recover
the passphrase. When using the offline attack, if the AP is vulnerable,
it may take only a matter of seconds to minutes.
feedback and OK already some time ago sthen@, gonzalo@
Pixiewps is a tool written in C used to bruteforce offline the WPS PIN
exploiting the low or non-existing entropy of some software
implementations, the so-called "pixie-dust attack" discovered by
Dominique Bongard in summer 2014. It is meant for educational purposes
only.
As opposed to the traditional online brute-force attack, implemented in
tools like Reaver or Bully which aim to recover the pin in a few hours,
this method can get the PIN in only a matter of seconds or minutes,
depending on the target, if vulnerable.
feedback and OK already a while ago sthen@, gonzalo@
appropriate in various devel/proj consumers to fix build with upcoming
proj 6 update, which will be commited in a month or so.
Thx to https://github.com/OSGeo/proj.4/wiki/proj.h-adoption-status for
linking the various upstream issues about it.
Remove the symbol renaming workaround. Use version scripts as done on
Linux and FreeBSD to hide internal symbols (eg HMAC_Update) that
conflict with libcrypto.
Tested in a bul by ajacoutot@, ok sthen@ naddy@, no objection landry@
(maintainer)
in PLISTs to avoid a conflict with "COMPILER" used in bsd.port.mk,
remove a hackish workaround, and allow COMPILER to be used as intended.
Use COMPILER to build with ports-gcc on !base-clang arches, needed with
-wx on these arches.
ok cwen@
- add spaces around BAR in "foo"BAR"foo"
- #include <new> in a higher-up header, avoiding namespace issue with
fancy_abort (sort-of borrowed from FreeBSD gcc ports)
