We NEED your help!
From the beginning, hashes have been using an incremental numbered format. This worked well when there were 10 or 20 types, but as support for hashtypes grows, we need YOUR help to come up with a more logical way of doing this.
The problem is as follows:
MD5 is currently grouped in increments of 10. Plain MD5 is as we know '0'. For each salted type, we add 10. This becomes an issue once we get 9 salted types because SHA occupies 100+.
The fragmentation becomes apparent when you see MD5crypt, which has a base of MD5, numbered as 500, or, SHA256/512crypt as 7400, and 1800 respectively.
We have mulled over this for the better part of 6 months with no clear solution. Previously, we had just realigned the numbers to create a standardization between hashcat and oclHashcat-*, but it is clear this method should be changed.
So we ask you, the users, for input on how you think this could be better accomplished. I'll leave this thread open for posts with your opinions, and the dev team will take your recommendations into consideration and credit the selection (if any) in the release that implements the change.
From the beginning, hashes have been using an incremental numbered format. This worked well when there were 10 or 20 types, but as support for hashtypes grows, we need YOUR help to come up with a more logical way of doing this.
The problem is as follows:
MD5 is currently grouped in increments of 10. Plain MD5 is as we know '0'. For each salted type, we add 10. This becomes an issue once we get 9 salted types because SHA occupies 100+.
The fragmentation becomes apparent when you see MD5crypt, which has a base of MD5, numbered as 500, or, SHA256/512crypt as 7400, and 1800 respectively.
We have mulled over this for the better part of 6 months with no clear solution. Previously, we had just realigned the numbers to create a standardization between hashcat and oclHashcat-*, but it is clear this method should be changed.
So we ask you, the users, for input on how you think this could be better accomplished. I'll leave this thread open for posts with your opinions, and the dev team will take your recommendations into consideration and credit the selection (if any) in the release that implements the change.