-m 15300 reworked + splitted in 15300/15900 #1365
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi fellow hash crackers,
I splitted my implementation of DPAPI masterkey file in hashcat in 2 separate formats:
Performances should not be impacted (a bit better though, as a conditionnal branchment was removed in the __loop workload) but this is better for visibility and real performances evaluation while doing benchmarks.
Indeed version 1, which concerns DPAPI until Microsoft Vista (and workstations that migrated from XP or Vista), is using hmac-sha1 and 3DES, whereas version 2, which concerns DPAPI beginning with 7, is using hmac-sha512 and AES256.
Thus perfomances vary between these 2 versions (even if the Windows 10 client version is not that worse compared with Vista, which is quite a fail...).
Cheers!
PS: all tests have been successfully passed with test.pl