02-01-2021, 06:52 AM
This is a known behavior and I'm not sure if it was decided if it was a bug or not. The reason is because the rule engine that runs on the GPU (-r) takes place AFTER the candidates are loaded. But the automatic rejection for the candidates happens host side BEFORE they make it to the GPU. This is the optimal order for performance but leads to some specific issues like the one you are having. The solution to this in your specific case would probably be to change to a full mask or mask file instead of using rules/wordlists. This would solve the issue as well as being faster overall than rules/wordlists would have been regardless. I will need to do some digging and reevaluate whether there is a fast way to fix this without a complete restructure of how the candidates are loaded and without doing the rejections on the GPU.