Open GoogleCodeExporter opened 9 years ago
The wordlist hanging issue was due to the fact that each time, fern tries to
calculate the number of lines in the wordlist, so when the file is very large,
it takes more time to calculate...
Replaced that function with an estimator function, so the issue has been
fixed... I have not released an update tag with this change so you have to
press on the update button to get the changes.
Original comment by savioboy...@gmail.com
on 6 Nov 2012 at 10:46
Also Thank you very much for the suggestion, ill keep them in mind :)
Original comment by savioboy...@gmail.com
on 6 Nov 2012 at 10:48
Thank you, and keep the good work :)
Original comment by etig...@gmail.com
on 8 Nov 2012 at 9:37
does this issue still exist? I have updated Fern from the update button to the
latest version but once I have successfully obtained a handshake, and Fern
starts brute forcing through the wordlist, it will freeze and hang on the same
word every time. From darkc0de list it stops on zygamasium or some word like
that. Only once has the program run further than that but still froze about 3/4
through the list.
Original comment by webst...@unlv.nevada.edu
on 20 Nov 2012 at 7:02
Ill look into this error, Please give me sometime
Original comment by savioboy...@gmail.com
on 23 Nov 2012 at 9:43
@webst...@unlv.nevada.edu
The error has been fixed.. the function that controlled the progress bar was
not giving accurate results, so when the progress stopped at the middle
(zygamasium) all the words in the wordlist had actually all been tested...
Replaced the faulty function with a more accurate more..
Original comment by savioboy...@gmail.com
on 20 Feb 2013 at 9:16
Still having this problem. With worldlist near 1 gb never get the 100%. I think
it's beacause the estimator function....
Running latest Fern Wifi Cracker 1.9 build
Original comment by matiasig...@meridiem.com.ar
on 12 Aug 2013 at 12:02
Attachments:
I'll look more into the error to find a fix...sorry for the delayed reply
Original comment by savioboy...@gmail.com
on 20 Aug 2013 at 5:58
Original issue reported on code.google.com by
etig...@gmail.com
on 6 Nov 2012 at 11:03