Solar Designer

While at it, we could also want to support the `{ARGON2}` prefix used by `slappw-argon2 - Argon2 password module to slapd`: https://man.archlinux.org/man/core/openldap/slappw-argon2.5.en ``` Both userPassword LDAP attributes below encode the...

Our users keep running into this issue and are confused and we spend time explaining that they have to use the OpenCL format. We'd very much appreciate work on this...

Maybe rather than add functionality to the CPU format, we should deprecate the recovery key support in the OpenCL format and bitlocker2john - e.g., have them print warnings that people...

I just noticed that while BitLocker-OpenCL had minimum password length and default benchmark password length set to 8, we didn't have a minimum in our BitLocker CPU format and we...

This was tricky to figure out, but looks easy if we accept the side-effects as desirable: ```diff commit cd8d511847dca14d0cbadabc2d6587ae99cf5352 (HEAD -> fixes-20240923) Author: Solar Date: Mon Sep 23 02:50:30 2024...

> Are you saying it somehow doesn't behave like `-w -ru -rules-stack=o1`? Yes. `./john pw -rules-stack=o1` vs. `./john pw -w -ru -rules-stack=o1` behave differently - the former feels somewhat unresponsive...

Re-opening so that we don't forget to look into the new (or remaining) weirdness further, although we may instead want to open a separate issue for that (please feel free...

I think I've just fixed the `--rules-stack` weirdness by adding `FLG_BATCH_CHK` checks to the 4 places in `rules.c` where we determine `rules_stacked_after`. Alternatively, we could temporarily set `FLG_RULES_CHK` in pass...

> I still get the out of order stats: Is this related to my allowing for stacked rules in batch mode or is it a separate/older issue?

@magnumripper Since the remaining issue is much older, I suggest we close this issue and you may open a separate issue/PR for that older issue.