Please note, this is a STATIC archive of website hashcat.net from 08 Oct 2020, cach3.com does not collect or store any user information, there is no "phishing" involved.

hashcat Forum

Full Version: Bug or Question, not sure
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Seems all I'm posting these days is bug questions, I'm beginning to feel like an entomologist! LOL

Same specs as last post: running gui 2.453 with 0.35
was doing a BF run last night with password length set 4min-5max and a chr set of UPPER Number Special:

ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789!@#$%^&*()-_+=~`[]{}|\:;"'<>,.?/ In EXACTLY this order. First thing I noticed when I started the run and the command window displayed the chrset it looked like this:
ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789!@#$%^&*()-_+=~`[]{}|\:;^<^>,.?/ so it seems the single and double quotes got replaced buy the ^ thingy and also moved the single quote between the greater and less than signs. so I figure what the hell and run it anyway. So far so good,the run works and I dec many of the 8500 hashes in the file. Looking at this run u would think that every 5 chr password that had UPPERNumSpecial chr's only, would be found. so this morning, (being a LOT more sober, and a little more alert), I checked the dec's against the password list and found I still had some 5chr UPPERNumSpecial passwords undecrypted. Thinking this strange I started a new run using the same chrset with min 4 and max 6 for the length and i'll be dammned if it didnt find more 5 chr passwords?? TOO freakin wierd!
It found 11 more to be exact, and they were all new ones that wern't in my master list, (my master list is from a run I did on the same hashes a month ago), but it did not find any of the ones that were left over from the run last night. Also last night and today it found passes with a single quote, ' , in them but not a single one had a double, " , quote in them, (and I know there are lots of passes that have double quotes), again from my master list. I realize that my chrset is not in ASCII format, and that this might be part of the reason for what's happening but have not checked because i'm still in the middle of this mornings run, ( it wont be finished for 5.5 more hrs). So heres the ? Seeing as how in the command window it changed both quotes to ^, first is this a bug or an ASCII order problem? and second why am i getting passes with single quotes in them and not getting the ones with double quotes??? Again, thanks for any and all help!!
indeed, the quoting on windows is a bit strange. i use a wrapper script for my runs to avoid dealing with escape chars in windows Smile but it should not find more passwords when running it multiple times. are you 100% sure you did the same command? maybe you changed something on quoting. i need something to reproduce!
ok here are some of the hashes and passes; the first 4 passes not found, second are found today doing the 4-6 run. hope this helps,also as u can see none with " in them.

047ccdf1e02771020703cecdd1172aab:"!M4L
7f59ab8b73e2d035b2a02b5e0828c928:"<JA5
a64e603d00e72e31f3924254f8658b3f:$N\*"[
030a5735d71147f744e88f35abd10e3eSmile2!8"Y oops sorry here it is )2!8"Y

d93a0d40bda83a29099b0dc218647895:$'5;A/
5061680133850ed5536cbdc239598f8d:FO;VF/
d6816e69b0093f78e84cf192b07f8152:EY)9O/
29c27e7509e26a4f91750e64eadedfd7:/6+'R
i hardly tried to reproduce this but i cant. everything works fine, here is my log. maybe i did something wrong? could you please verify?

Quote:atom@hashcat:~/hashcat-0.36$ cat > hash
047ccdf1e02771020703cecdd1172aab
7f59ab8b73e2d035b2a02b5e0828c928
a64e603d00e72e31f3924254f8658b3f
030a5735d71147f744e88f35abd10e3e
d93a0d40bda83a29099b0dc218647895
5061680133850ed5536cbdc239598f8d
d6816e69b0093f78e84cf192b07f8152
29c27e7509e26a4f91750e64eadedfd7

atom@hashcat:~/hashcat-0.36$ export CS=`perl -e 'my $x; for (0x20..0x7e) { $x .= chr }; $x =~ s/[a-z]//g; print $x'`

atom@hashcat:~/hashcat-0.36$ echo $CS
!"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`{|}~

atom@hashcat:~/hashcat-0.36$ ./hashcat-cli32.bin -m 1000 -n 12 -a 3 --bf-cs-buf="$CS" hash --bf-pw-min=5 --bf-pw-max=5
047ccdf1e02771020703cecdd1172aab:"!M4L
7f59ab8b73e2d035b2a02b5e0828c928:"<JA5
Charset...: !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`{|}~
Length....: 5
Index.....: 0/1 (segment), 1564031349 (words), 0 (bytes)
Recovered.: 2/8 hashes, 0/1 salts
Speed/sec.: - plains, 93.95M words
Progress..: 1564031349/1564031349 (100.00%)
Running...: 00:00:00:16
Estimated.: --:--:--:--
Started: Tue Mar 29 19:26:31 2011
Stopped: Tue Mar 29 19:26:47 2011

atom@hashcat:~/hashcat-0.36$ ./hashcat-cli32.bin -m 1000 -n 12 -a 3 --bf-cs-buf="$CS" hash --bf-pw-min=4 --bf-pw-max=6
Initializing with 12 threads and 32mb segment-size...

NOTE: press enter for status-screen

Added hashes from file hash: 8 (1 salts)
Charset...: !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`{|}~
Length....: 4
Index.....: 0/1 (segment), 22667121 (words), 0 (bytes)
Recovered.: 0/8 hashes, 0/1 salts
Speed/sec.: - plains, 93.01M words
Progress..: 22667121/22667121 (100.00%)
Running...: 00:00:00:01
Estimated.: --:--:--:--
047ccdf1e02771020703cecdd1172aab:"!M4L
7f59ab8b73e2d035b2a02b5e0828c928:"<JA5
Charset...: !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`{|}~
Length....: 5
Index.....: 0/1 (segment), 1564031349 (words), 0 (bytes)
Recovered.: 2/8 hashes, 0/1 salts
Speed/sec.: - plains, 94.10M words
Progress..: 1564031349/1564031349 (100.00%)
Running...: 00:00:00:16
Estimated.: --:--:--:--
a64e603d00e72e31f3924254f8658b3f:$N\*"[
d93a0d40bda83a29099b0dc218647895:$'5;A/
5061680133850ed5536cbdc239598f8d:FO;VF/
d6816e69b0093f78e84cf192b07f8152:EY)9O/
29c27e7509e26a4f91750e64eadedfd7:/6+'R/
030a5735d71147f744e88f35abd10e3eSmile2!8"Y
All hashes have been recovered