08-15-2016, 01:54 PM
(This post was last modified: 08-15-2016, 08:33 PM by Kgx Pnqvhm.)
Update: Matt has a Sunday, August 14, 2016 blog post titled "Evaluating the Value of the (@)Purge Rule" at http://reusablesec.blogspot.com/2016/08/...-rule.html.
He states that "Since then, At0m added support for the rule back in the newest build of Hashcat" and gives a GitHub link.
My next question is do we want to run it on a CPU device or GPU device?
In other words, would it slow down the GPU processing, or is there no speed penalty?
Should we still reserve running the purge rules on CPU, as a separate rule set, just like the CPU hashcat vs. GPU cudahashcat division?
He states that "Since then, At0m added support for the rule back in the newest build of Hashcat" and gives a GitHub link.
My next question is do we want to run it on a CPU device or GPU device?
In other words, would it slow down the GPU processing, or is there no speed penalty?
Should we still reserve running the purge rules on CPU, as a separate rule set, just like the CPU hashcat vs. GPU cudahashcat division?