Wait, the output of a rule does not only depend on the rule itself, it also depends on the input word. For example if the input word is "password" as in your example, those rules do the same:
[/quote]
password:$_ E:Password_
password:i8_ E:Password_
[/quote]
But if the input word is "hello", the ruleas do the following:
That's why there's no way to automatically recognize if a rule really does the same thing. There's only one thing you can really do, that is if you find out if a rule is doing exactly the same thing as an other rule and then sort it out. There's an extra tool "rules_optimize" that comes with oclHashcat in the extra/ folder that removes unused function calls. After using this you get a bit a better sort -u hitrate. Read here for details: http://hashcat.net/forum/thread-3133.html
Btw, the cleanup-rule from hashcat-utils is not used for this task at all. It's used for sorting out rules that work on CPU but not on GPU.
[/quote]
password:$_ E:Password_
password:i8_ E:Password_
[/quote]
But if the input word is "hello", the ruleas do the following:
Quote:hello:$_ E:Hello_
hello:i8_ E:Hello
That's why there's no way to automatically recognize if a rule really does the same thing. There's only one thing you can really do, that is if you find out if a rule is doing exactly the same thing as an other rule and then sort it out. There's an extra tool "rules_optimize" that comes with oclHashcat in the extra/ folder that removes unused function calls. After using this you get a bit a better sort -u hitrate. Read here for details: http://hashcat.net/forum/thread-3133.html
Btw, the cleanup-rule from hashcat-utils is not used for this task at all. It's used for sorting out rules that work on CPU but not on GPU.