Jump to content

Craphoontio

Active Members
  • Posts

    3
  • Joined

  • Last visited

Recent Profile Visitors

228 profile views

Craphoontio's Achievements

Newbie

Newbie (1/14)

  1. And how is this related to reaver in any way? Reaver isn't collecting anything.
  2. It may look obvious, but I really can't get it. I must be missing a pretty big detail about network modes and the low level inner working of WPS, despite I read all of the papers I could find[1]. According to wikipedia, monitor mode is a mode that allows mostly only to listen without being associated to any access point or router (and if the hardware and the driver allows it too, to transmit as well, and there we have what's called packet injection). So far so good. When you try to bruteforce WPS PINS, though, you do associate with the AP first. At least, reaver does. So why you actually need to be in monitor mode? All WPS cracking program require it, so it's no doubt it's a necessity. All the tutorials out there just tell you to "do it" but none as I could find tells the why of that. Please help, I'd really love to understand it better :) Thanks so much! [1] Only two actually :P but one is Stefan Viehböck's original paper. The other is this transcript of a very nice talk: https://www.grc.com/sn/sn-337.htm
  3. It really looks like it's AP-dependent. It probably slows you down after N bad tries, whether you are pushing that fast or not. If so, there's nothing you can do actually. Well, perhaps changing the MAC address to see if the slow-down is related only to your MAC or not, and if so, make a wrapper script that tries N pins, change MAC address, and start over.
×
×
  • Create New...