10-28-2014, 06:29 PM
1. pls do not post hashes (even if they are from wiki etc, I don't want to look them up and it is just irrelevant, mask them if you really needed)
2. see the version of the hash that you think is used:
$office$*2013*100000...
versus the version that is actually used:
2013*100000...
3. since there is no indication of error in line x of file... I suppose you use this hash directly in the command line (this is my assumption, but this would be the most important thing you need to mention)
4. if you do so, i.e. hash directly in command line, you need to make sure that the shell does not interpret the single parts (or does other stuff with it) before oclHashcat sees it. For instance every $... in most common shells is called a use of a variable e.g. $office means, use the variable with name $office.
To avoid #4 you need to quote it '$office$*2013*100000...' etc.
If this is the case, why do you not test with a hash.txt file to make sure your command line is correct (and you do not need quotes/escapes etc)?
2. see the version of the hash that you think is used:
$office$*2013*100000...
versus the version that is actually used:
2013*100000...
3. since there is no indication of error in line x of file... I suppose you use this hash directly in the command line (this is my assumption, but this would be the most important thing you need to mention)
4. if you do so, i.e. hash directly in command line, you need to make sure that the shell does not interpret the single parts (or does other stuff with it) before oclHashcat sees it. For instance every $... in most common shells is called a use of a variable e.g. $office means, use the variable with name $office.
To avoid #4 you need to quote it '$office$*2013*100000...' etc.
If this is the case, why do you not test with a hash.txt file to make sure your command line is correct (and you do not need quotes/escapes etc)?