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!!
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!!