-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WPS networks not displaying as WPS networks #8
Comments
This is still broken in master, which basically kills a lot of the reason you would use this. Please reopen this @NovaCygni |
Possibly related (Pentoo, which uses wifite2 and reaver-wps-fork-t6x) ... Looks like reaver-wps-fork-t6x inverts the meaning of '-C' command in wash, hence nothing shows up as WPS-capable in wifite2 when using that version. |
@NovaCygni What version of reaver is Wifite2 meant to use? |
Removing my previous comment. reaver fork guys seems agreed to revert it: P.S. Need to wait https://www.youtube.com/watch?v=vifwar7jxcQ |
@yuri-sevatz It was supposed to use the t6x-github fork but derv appears to have gone awol on this project. If you want im planning on actually redoing the whole Wifite and the required Reaver as a StandAlone "Wifite3" in Python 3.5, so far willing contributors appears to be just myself but id love a extra hand working on it. |
I'm highly interested in a new version that has a focus on error checking. Is py3 out of familiarity? |
@weedy Partially but also because itl allow Async to be used so when a error is thrown rather than Except to deal with it I can use "Await" to chain the fix for error thrown then continue on which would be alot more efficient as it means fewer dropped exchanges due to timeout... nothing worse than a couple M2 or M3 out of Sync that causes an entire false "Run Through". Id love to check the "Ugly Edits" :p Always amazed me what little gems of genius people casually put in to solve x problem :) |
Please do not call wash with "-C" parameter. This is a default behaviour now and the flag has been removed (i.e. it will throw an error) |
Also got this error. Removed the |
i was getting WPS networks displayed until the recent change, now i get none |
|
wps is displaying fine with the new change the change before it was displaying no under the wps column wash 2>/dev/null | head -5 |
Ok cool. Closing this issue, but anyone can reopen if it's still a problem. |
@derv82 users are getting lost between wifite(which is outdated and broken), wifite-fork (with non-technical and unfriendly developers) and wifite2. Can you take an initiative, port back any changes from the fork and release a one version which actually works? |
@blshkv Are you asking for an update to the old wifite? I'm choosing to ignore the old version of I created #19 for tracking the backport of features from wifite forks into this repo ( Feel free to create a new issue for each feature you want Wifite2 to have. |
I'm asking to put a bit more afford into |
Im looking into the issue atm of the WPS networks not being detected as WPS thus, unable to be attacked when they should be able to, roughly know whats causing it so ill leave this bug-report open till ive submitted the code changes required to fix this issue (* will likely change the WPS method in 2 ways, 1) use Wash to confirm Lock status 2) allow a "IgnoreWPSNotDetected" toggle to attempt attacks on routers regardless of WPS status *)
The text was updated successfully, but these errors were encountered: