Chick3nman

What about a compromise where for presale we state that the hash _IS_ dangerous but then for the other 2 we state that the hash _MAY_ be dangerous due to...

Our current message does say "may" as it is, so I'm not sure the distinction will do very much really.

This threshold was chosen because under ~1000 it didn't seem necessary to inform the user of those values because you can quickly spot check and do the conversion in your...

> If I start a long running task on 999 hashes, go to bed, and come back to a hash list with 58/941. How many cracks per hour is that?...

> Not necessarily. JSON output doesn't have the `Recovered/Time` values at the moment, for example. Neither they are displayed with `--machine-readable`. Not really sure if that's relevant to the core...

@b8vr The limit for rule functions is 31 operations, i think having to dedicate 10 or so to replacements to achieve this is not too unreasonable. The main issue that...

Ah yeah, I do see how it becomes all 0s, you are correct. I had already copied the inverted one to test with the place holder and not the original...

Your hash appears to be invalid, there's a bunch of junk in the middle of it. That would be why you are getting the exception.

Unfortunately, you aren't even seeing the "fully" expanded display in your first example. ``` Recovered........: 8/247 (3.24%) Digests (total), 0/247 (0.00%) Digests (new), 8/247 (3.24%) Salts ``` This is why...

Currently the code that handles stdout doesn't account for the use of --slow-candidates mode and, seeing as how it's mostly done host side anyway, I don't think it should as...