-
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
Wifite crash for python3 --crack #157
Comments
Great. I suggest these "crashes" should have better output on what's really going on and possibly a solution on the matter. Great find, sure @derv82 return soon. |
RaduNico
added a commit
to RaduNico/wifite2
that referenced
this issue
Oct 19, 2018
Wifite would crash if run with python3 and the parameter --crack if a dependency was missing, just after selecting a target. This was caused by popping from a dictionary while iterating on it, an operation forbidden in python3. Issue described in derv82#157 Signed-off-by: Radu Nicolau <[email protected]>
RaduNico
added a commit
to RaduNico/wifite2
that referenced
this issue
Feb 26, 2019
Wifite would crash if run with python3 and the parameter --crack if a dependency was missing, just after selecting a target. This was caused by popping from a dictionary while iterating on it, an operation forbidden in python3. Issue described in derv82#157 Signed-off-by: Radu Nicolau <[email protected]>
mendelgusmao
pushed a commit
to mendelgusmao/wifite2
that referenced
this issue
Oct 21, 2024
…s-68.0.0 build(deps): bump setuptools from 67.8.0 to 68.0.0
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Running wifite --crack under python3 while having a missing dependency (aircrack, john, cowpatty, hashcat) will result in this crash error. The issue is utiil/crack.py, a dictionary is created with all the dependecies and if one is missing, the values is popped from the dict. While in python 2 this is not an issue in python 3 it results in a crash.
I will make a fix for this issue tomorrow morning.
The text was updated successfully, but these errors were encountered: