Poll: Which Feature / Algo to add next to oclHashcat?
You do not have permission to vote in this poll.
Feature: password length range support
16.22%
6 16.22%
Feature: delete a hash from the hashlist once it is cracked
24.32%
9 24.32%
Feature: make -l more precise
2.70%
1 2.70%
Feature: define a fixed salt length
5.41%
2 5.41%
Feature: increase password length limitation
2.70%
1 2.70%
Algo: DES
16.22%
6 16.22%
Algo: MD5(Wordpress) / MD5(phpBB3)
10.81%
4 10.81%
Algo: SHA-256
13.51%
5 13.51%
Algo: md5(md5($salt).md5($pass))
5.41%
2 5.41%
Algo: Whirlpool
2.70%
1 2.70%
Total 37 vote(s) 100%
* You voted for this item. [Show Results]

Which Feature / Algo to add next to oclHashcat?
#10
I would propose the implementation of the UX DES and LMNT as a end solution for these algorithms. UX DES is normally limited to a length of 8 characters LMNT turn seven characters (You can then delete the few giga rainbow tables for lm-charset cp437-FRT-850).

As for me personally for a maximum password recovery realized UX MD5, BF UX and standard ZIP (not AES). Anything would be happy with that.


Messages In This Thread
RE: Which Feature / Algo to add next to oclHashcat? - by Dr-Tibetor - 07-07-2010, 03:37 PM