-
-
Notifications
You must be signed in to change notification settings - Fork 46
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
s109 drops 500 in report #183
Comments
I would guess it's a non utf8 conform byte that causes the issue. Can you:
|
There are more log files, I don't know which one should I check. :( Lines in emba_run.log with (Bad file descriptor) are very strange because of the huge repetitions. But it is not connecting to http 500 I believe. |
Sorry, |
Yes, UnicodeDecodeError exists more times in the file:( |
Will try to solve this in EMBA directly |
@torabi12 could you provide me with the firmware for testing? |
Please download it from here: https://drive.google.com/file/d/1jXqPpg_z8ghZG0XPxtx-qtl2Mx_N2FL1/view?usp=sharing I used Top109Million-probable-v2.txt as jtr_wordlist.txt from here: https://github.com/berzerk0/Probable-Wordlists/tree/master/Real-Passwords and I added manually the good password at the end of the file. This is the password file: https://drive.google.com/file/d/11q3ARlr9fL4Fh_hqrUFXTfG-xbOw_6oD/view?usp=sharing You should add the "p9z34c" value at the end and emba will find it, if you would like to reproduce the whole test from my side. |
It can happen that I used a not supported password file and that caused this issue. I am going to try the same test with a basic password list and let you know the outcome soon. |
Hmm, I used rockyou.txt with adding the good password to the last line and the s109 cracked it and the page is available: Looks like I used a not supported password list. :( |
@BenediktMKuehne good work |
The changes affect only s109 and s99 (jtr and grepit modules) |
Describe the bug
I did a short scan and "Cracking identified password hashes" menu dropped 500 in the browser. The s109_jtr_local_pw_cracking.html exists in the file system and contains the good password. Only the page is not displayed.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Display page for s109.
Screenshots
Desktop (please complete the following information):
Additional context
s109_jtr_local_pw_cracking.txt
The text was updated successfully, but these errors were encountered: