08-02-2017, 10:56 AM
Yeah, you are right it sometimes depends on how "experimental" the beta currently is. Sometimes (actually very often) betas contain fixes for known problems/bugs and therefore at that very moment we recommend to use betas such that the user doesn't experience the problem (and the user can confirm that the beta version fixed the problem).
Other times, the betas are (very) experimental (like it is currently the case, since there were a lot of changes involving changes of max supported pass and salt length etc, see the github commit history for details).
There are some maximal values for passwords (also mentioned here: https://hashcat.net/wiki/doku.php?id=fre...ord_length).
In general, you should see within the status display if the password candidate was too long (have a look at the line labeled "Rejected").
You didn't really answer the question about if older and/or the current release version was able to crack your hash. You also didn't mention if the example hash works for you.
Other times, the betas are (very) experimental (like it is currently the case, since there were a lot of changes involving changes of max supported pass and salt length etc, see the github commit history for details).
There are some maximal values for passwords (also mentioned here: https://hashcat.net/wiki/doku.php?id=fre...ord_length).
In general, you should see within the status display if the password candidate was too long (have a look at the line labeled "Rejected").
You didn't really answer the question about if older and/or the current release version was able to crack your hash. You also didn't mention if the example hash works for you.