HC and Blowfish Advanced CS Help

[womble]

@womble, do you plan on sharing your hashcat module and opening a pull request (PR) on github ?

Yes, although I'm in no hurry given that my other PRs don't seem to have gotten any eyeballs.

what is your strategy with avoiding false positive (or can we assume that it's quite rare and the user should use --keep-guessing ?)

It'll have to be --keep-guessing. There's not really any other way that'll work.

btw: also see https://github.com/hashcat/hashcat/blob/...t-guide.md for our new dev guide, we would appreciate some feedback or help in improving it also. that would be great (but remember, it's a guide... not a tutorial or step-by-step instruction on how to add a module)

It's excellent. Helped me immensely when I was writing the PKCS#1 module.

It would also be nice to have some standard hash format for it.... lately we tend to use hash formats with signature like:
$BFACS$version*salt*data*hash

I've used $bfacs$<salt>$<check>. Not rocket science to change, though, if necessary. I don't think a version is necessary here, as the last release was aaaaaaaaaaaaaages ago.

I think it wouldn't be impossible to use the MD5 checksum as a early reject/exit, but later on also do some further verification (only if matched)... not sure if a strategy like this is possible/applicable here (I didn't look at the details)

I don't think it's feasible. You can encrypt *anything* with this tool, so there's no known plaintext we can use to decide if we've got the right passphrase, and even an entropy check won't work (because the plaintext could be compressed or another encrypted blob or whatever).