11-17-2011, 04:49 PM
Atom would you please consider this feature in hashcatplus ?
Currently if a user wishes to modify their wordlists, on the fly, in hashcatplus they can use rules.
This is a very powerful and useful feature but it has one slight draw back. The rule files can get very long and complex even for very simple and common password modifications.
For example, say the user wants a simple modification to their lists.
Rule File
l
u
c
In the above rule we see that the user wishes to lower case all, upper case all and then capitalise the first letter of each line of their wordlist. Fortunately this only requires 3 lines of rule code. The problem arises when a user decides to make another seemingly simple modification to their word list, appending numbers to the password.
Number suffixing is very common so it is not unreasonable to want to do this, say 0 – 100. The problem is by simply wanting to append a small number range to a password whilst also retaining the previous (very common) modifications l,u,c this rule list is already about 300 lines long ! Another, simple and common password padding is appending years, “bob1960†for example. So to catch these words with the rule file l,u,c we are already running into 3000 lines, 4000 if we include an original pass “:â€.
So can I make a feature request that allows “Rule Piping†? This will allow users to have a primary and secondary rule file.
Example code would look like…
oclHashcat-plus32.exe --hash-type 2500 examplewpa.hccap wordlist.txt --rules-file example.rule --rules-file2 example.rule -o Found.txt
(If no “--rules-file2 example.rule†exists then hashcatplus would work as it does now and assume a single rule file).
Rulefile1 > password Rulefile2 > output . Rules are taken from lists 1 and run down the entire list 2, then the second rule is taken from list 1 and run down list 2 and so on.
Rule file 1 contains l,u,c while rule file 2 contains $0 - $1$0$0
The combined first rule sent to the engine would be l so Password would be all lower case, then rule 2 would append a number 0 result = password0.
The above would allow for considerably smaller rule lists (3 lines in list 1 and 100 lines in list 2) which offer other possibilities which will also be very helpful when using the toggle rule.
I was going to suggest a rule that appended numbers that only took one line to write something like $num0-100 or similar but I think piping one list into the other offers more flexibility.
Better rules and rule management mean more rules for the GPU thus (hopefully) optimising it. !!
Thank you.
Currently if a user wishes to modify their wordlists, on the fly, in hashcatplus they can use rules.
This is a very powerful and useful feature but it has one slight draw back. The rule files can get very long and complex even for very simple and common password modifications.
For example, say the user wants a simple modification to their lists.
Rule File
l
u
c
In the above rule we see that the user wishes to lower case all, upper case all and then capitalise the first letter of each line of their wordlist. Fortunately this only requires 3 lines of rule code. The problem arises when a user decides to make another seemingly simple modification to their word list, appending numbers to the password.
Number suffixing is very common so it is not unreasonable to want to do this, say 0 – 100. The problem is by simply wanting to append a small number range to a password whilst also retaining the previous (very common) modifications l,u,c this rule list is already about 300 lines long ! Another, simple and common password padding is appending years, “bob1960†for example. So to catch these words with the rule file l,u,c we are already running into 3000 lines, 4000 if we include an original pass “:â€.
So can I make a feature request that allows “Rule Piping†? This will allow users to have a primary and secondary rule file.
Example code would look like…
oclHashcat-plus32.exe --hash-type 2500 examplewpa.hccap wordlist.txt --rules-file example.rule --rules-file2 example.rule -o Found.txt
(If no “--rules-file2 example.rule†exists then hashcatplus would work as it does now and assume a single rule file).
Rulefile1 > password Rulefile2 > output . Rules are taken from lists 1 and run down the entire list 2, then the second rule is taken from list 1 and run down list 2 and so on.
Rule file 1 contains l,u,c while rule file 2 contains $0 - $1$0$0
The combined first rule sent to the engine would be l so Password would be all lower case, then rule 2 would append a number 0 result = password0.
The above would allow for considerably smaller rule lists (3 lines in list 1 and 100 lines in list 2) which offer other possibilities which will also be very helpful when using the toggle rule.
I was going to suggest a rule that appended numbers that only took one line to write something like $num0-100 or similar but I think piping one list into the other offers more flexibility.
Better rules and rule management mean more rules for the GPU thus (hopefully) optimising it. !!
Thank you.