Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Test-PasswordQuality directly with SPLIT database from HIBP #185

Open
gruppenrichtlinien opened this issue Sep 13, 2024 · 3 comments · May be fixed by #186
Open

Test-PasswordQuality directly with SPLIT database from HIBP #185

gruppenrichtlinien opened this issue Sep 13, 2024 · 3 comments · May be fixed by #186

Comments

@gruppenrichtlinien
Copy link

Test-PasswordQuality and the parameter -WeakPasswordHashesSortedFile or -WeakPasswordHashesFile is using the single file, e.g. fom HIBP.

Actually I use two seperate versions of the HIBP File: Single and Split into 00000-FFFFF.txt, the SPLIT files are more performant, when checking how often the hash is in the breached list.

For Data Reduction reasons, it would be nice to have only the split version and a parameter like " -WeakPasswordHashesFilePath"

@MichaelGrafnetter
Copy link
Owner

Hello @gruppenrichtlinien , would you please be able to implement this feature?

@gruppenrichtlinien
Copy link
Author

gruppenrichtlinien commented Oct 29, 2024

Sorry, I think it´s my problem in understanding.

The reason, why I use the split files is, not to get the count of compromised accounts in the AD. The reason to use the split is the faster search for the counter how often a specific NTLM hash is inside the database.
An appearence of 10.000+ is much more faster to reset, than one with a count of 10.

the counter is inside the .txt files, seperated by ":"

If I search for the specific Hash in 30GB it took a long time ...

Thanks for adding the Parameter -WeakPasswordHashesSortedFilePath ! :-)

@aseigler
Copy link
Contributor

Understood. It's implemented in #186.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants