Page 3 of 13 FirstFirst 12345 ... LastLast
Results 21 to 30 of 123

Thread: Wifite including new pixiewps attack

  1. #21
    Senior Member
    Join Date
    Mar 2015
    Posts
    138
    Yeah, didn't exit the loop properly, oops! O.o
    Should be all fixed now

  2. #22
    Junior Member
    Join Date
    Nov 2014
    Posts
    7
    @aanarchyy,
    Is your Wifite based on derv82 's code?
    As I recall bwall, drone and brianpow consecutively modified the Wifite code to r95.
    Latest Wifite was on https://github.com/brianpow/wifite afaik...
    Last edited by SubZero5; 2015-04-21 at 07:16 AM.

  3. #23
    Senior Member
    Join Date
    Mar 2015
    Posts
    127
    Posted two new issues to your git, aanarchyy.

    Question - if wifite finds a client, does it spoof the mac of client?
    Question - if mon0 is already started a fake mac address, does wifite pass the fake/spoofed mac address when using reaver (ex. reaver -i mon0 -b 11:22:33:44:55:66 --mac=00:11:00:11:00:11 -vv -S -K1)

  4. #24
    Senior Member
    Join Date
    Mar 2015
    Posts
    127
    deleted double post
    Last edited by nuroo; 2015-04-21 at 12:41 PM. Reason: double post

  5. #25
    Senior Member
    Join Date
    Mar 2015
    Posts
    127
    Quote Originally Posted by SubZero5 View Post
    @aanarchyy,
    Is your Wifite based on derv82 's code?
    As I recall bwall, drone and brianpow consecutively modified the Wifite code to r95.
    Latest Wifite was on https://github.com/brianpow/wifite afaik...
    just checked out that version SubZero. Nice. alots of cool improvements. But it came out b4 pixiewps and modded reaver, so lacking that functionality.

  6. #26
    Senior Member
    Join Date
    Mar 2015
    Posts
    138
    @Subzero5
    The one i am working with is the one that came on Kali. I may update it and add my patches in soon. Any specific features in that one?

    @nuroo
    1) No, but that was an idea i had been thinking of adding in.
    2) If it's already spoofed, there is no reason to use the --mac flag as it is already spoofed.
    3) Check the first issue you posted on github and confirm it's fixed for me please :-)

    Updated to now run reaver automatically unless explicitly told to skip psk retrevial vai -pixienopsk flag

    Still trying to figure out the whole updating timer thing, picking up python as i go along here
    Last edited by aanarchyy; 2015-04-21 at 03:45 PM.

  7. #27
    Senior Member
    Join Date
    Mar 2015
    Posts
    127
    Im pretty sure reaver doesnt use spoofed mac address for monitor unless --mac option is given.


    i'll test for same issue now. but maybe results later, quick lunch

  8. #28
    Senior Member
    Join Date
    Mar 2015
    Posts
    127
    airmon-ng also does not copy spoofed mac address to monitor. after airmon-ng creates monitor, i still take it down and run macchanger and assign same spoofed mac address to monitor. that is the reason I always create monitor before running wifite........i believe thats the reason for --mac in reaver.
    Last edited by nuroo; 2015-04-21 at 06:05 PM.

  9. #29
    Senior Member
    Join Date
    Mar 2015
    Posts
    127
    Consider a version or revision number.....for us track changes/fixes. and to know if im reporting on current revision.

  10. #30
    Senior Member
    Join Date
    Mar 2015
    Posts
    138
    What behavior were you thinking for the spoofing part?

    Specify address to spoof at command line?
    Wait until client found then start attack with spoofed address?
    Start attacking unspoofed and watch at same time, and when client found, restart attack with spoofed address?
    If multiple clients found, rotate addresses so often?

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •