This is follow up of #1969 intended as a discussion on how this rule should behave.
It would be great if @jfoug and/or @magnumripper would join so we can battle it out and make it consistent between hashcat and john.

As I mentioned in the original report I assumed that given the input word foobar and the rule ef the mangled output should be FOobar. This is based on my first thought when

See #4243. We can use hccap/hccapx files, but normally I'd recommend using wpapcap2john if you do have a pcap at all. That, or (possibly even better) something from hcxtools which we could also mention (Zerobeat's hcxdumptool is the absolute best sniffer for WPA as well).

Winxp, need to redo Server and Client Documentation

Wiki should be updated to inform users the C# client is technically Depreciated at this time and current wiki should be converted to using the python client as its main focus ( Or make the link to the Client repo much more apparent ((probably the best option)))

Videos should be rather generic on setup Pointing users to use commands found

Hi,

The analyzer crashes here for me with a specific binary. The issue is that in my case the szDisasmText content is 273 characters long, while GuiInstruction can't hold that much.

Perhaps GuiInstruction's size needs to be changed from [MAX_MNEMONIC_SIZE * 4](https:/

"Credential confirmation" should be replaced with "Combolist".

We might want to rename the subcommand as well, from badtouch creds to badtouch combo, but if we do this we should still accept creds as an alias.

cGFzc3dvcmQy (base64 for password2) string returns ✖ Hash type not supported
The problem probably lies in this regex

Add a little pop-up when you leave the mouse over a rule/word list. The pop-up would contain a description of the element which is indicated by the mouse.

I guess the descriptions need to be configurable/added in some way.