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?
#9
all right we have a winner. i will add the feature "delete a hash from the hashlist once it is cracked". if i have some time left maybe "password length range support" as well. otherwise it will show up again in the next poll.

i recognized the votes on DES. anyway, i will remove DES(Unix) from the next oclHashcat poll. but i will add it to hashcat cpu. reason for that is my tests with bitsliced DES was nearly equal in speed on GPU and on CPU (i did not spend much time on optimizing). even it is still a common used hash in htaccess i think its popularity will drop in the future. it is already replaced in most linux distributions by md5(unix) or sha512. i think its better to spend time into these newer and stronger hashes. however, oclHashcat features have priority over this.

thanks for voting on the poll. it clearly shows a direction. dont forget to vote on next poll, too Smile

--
atom


Messages In This Thread
RE: Which Feature / Algo to add next to oclHashcat? - by atom - 07-03-2010, 06:50 PM