02-15-2019, 09:39 AM
as you might already know, if you use any amplifier (like rules) the total number of password candidates will increase. This implies also that the "Progress" number in the status screen will get larger and larger the more rules you use.
The "crackpos" value will take this offset into account too. i.e. it won't only reflect the word position but also the word_pos * rule_pos etc... I think you get the idea (to get the full technical details I would recommend looking into the source code file e.g. src/outfile.c etc).
There is one caveat, crackpos must be considered as an indicator that helps for statistical/forensic/analysis purposes and should be treated as an indicator which passwords are cracked first (or which are easier to crack etc).
Of course it could in theory give slightly different results if you test with different systems and/or different GPUs on a system whenever for instance multiple rule+word combinations would crack the same hash etc.
Statistically viewing it it's a quite robust/good indicator, but of course since the password cracking is highly parallelized there could be different "crackpos" reported during different launches (especially if you have multiple GPUs or are comparing it with different machines etc).
At the end it's a negligible offset of course (if any), but that's how "crackpos" was intended to be used i.e. only to see which passwords are easier to crack compared to others etc.
The "crackpos" value will take this offset into account too. i.e. it won't only reflect the word position but also the word_pos * rule_pos etc... I think you get the idea (to get the full technical details I would recommend looking into the source code file e.g. src/outfile.c etc).
There is one caveat, crackpos must be considered as an indicator that helps for statistical/forensic/analysis purposes and should be treated as an indicator which passwords are cracked first (or which are easier to crack etc).
Of course it could in theory give slightly different results if you test with different systems and/or different GPUs on a system whenever for instance multiple rule+word combinations would crack the same hash etc.
Statistically viewing it it's a quite robust/good indicator, but of course since the password cracking is highly parallelized there could be different "crackpos" reported during different launches (especially if you have multiple GPUs or are comparing it with different machines etc).
At the end it's a negligible offset of course (if any), but that's how "crackpos" was intended to be used i.e. only to see which passwords are easier to crack compared to others etc.