work or documentation changes needed for rule eX and e?C #3708
Labels
documentation
notes/external issues
portability
regression
Bug introduced with certain change(s), causing performance degradation or feature loss
This follows along with hashcat/hashcat#1970
Right now, there is some ambiguity on things, which have caused the 2 projects to return different values for the eX rule (HC does not have the e?C rule as it does not do classes).
At a minimum, we should document FULLY exactly how these rules work. We may need to change some code in rules, IF the user base expects certain behaviors.
FOR NOW, lets hold off on this, and see just where the logic is expected to go. Once that is finalized, then we can document EXACTLY what is to be expected, and if there are any changes needed to the rules.c, make them. It should hopefully be trivial changes. The CLASS macro suite has the framework done. We just have to get the 'true' and 'false' parts being passed into the macro working the way people expect the logic to be.
The text was updated successfully, but these errors were encountered: