04-16-2013, 03:36 PM
First of all, I am sure you've noticed that the forum adds newlines etc characters... So also the "show page source" feature of your browser includes some special characters (newline etc) in the string above...
You must get rid of all of that stuff, i.e. compare your pasted text and keep attention especially at the mark of new line (e.g after "da43" there should be *nothing* except "fa9a"... and so on).
That may be the first problem.
Second, it seems to be that the Windows version has a MAX line length of *around* (not totally sure, if my quick test was totally correct) 512 characters (@atom, maybe this is a max buffer size etc?)
If you have more than (around) 512 characters you will see in the output the error "... in line 2 ...". Also if there is no such line, e.g there is only *one* line (tested with cygwin wc).
So @atom, maybe you need to increase a buffer or similar to parse this input hashes on *windows*???
I now tried the *exactly* same hash input file hash.txt w/ ubuntu/linux and there it was cracked immediately w/o any error (scp from windows to linux s.t. I don't introduce errors).
You must get rid of all of that stuff, i.e. compare your pasted text and keep attention especially at the mark of new line (e.g after "da43" there should be *nothing* except "fa9a"... and so on).
That may be the first problem.
Second, it seems to be that the Windows version has a MAX line length of *around* (not totally sure, if my quick test was totally correct) 512 characters (@atom, maybe this is a max buffer size etc?)
If you have more than (around) 512 characters you will see in the output the error "... in line 2 ...". Also if there is no such line, e.g there is only *one* line (tested with cygwin wc).
So @atom, maybe you need to increase a buffer or similar to parse this input hashes on *windows*???
I now tried the *exactly* same hash input file hash.txt w/ ubuntu/linux and there it was cracked immediately w/o any error (scp from windows to linux s.t. I don't introduce errors).