Exhaustive password search and restart point

[kimci86]

• Implement exhaustive search (resolves Exhaustive password search #34)
• Ability to restart search after a non-exhaustive search or SIGINT (resolves Resuming a cancelled password recovery ? #35)
  • Make it more precise (the starting point is coarse for now)
• Print progress less often to improve performance
• Clean up implementation, profile and optimize
• Update documentation, readme, tutorial

[kimci86]

@geofjamg Could you try this version?
To do so, you can download the build artifcact from github actions or build this branch yourself and then run bkcrack with the -e flag to enable exhaustive search.

[cxzstuff]

Tried, took now 9 hours, before 8½ . Found it and continued. At 1452 instead of 1455/3844 like before. (That starting point option would help a lot.) Output a bit messy as color codes didn't work on windows.

bkcrack -k 6eda3a27 2edfbde4 237a1e01 -r 20 ?a -e
bkcrack 1.3.2 - 2021-11-02
[12:59:00] Recovering password
�[2Klength 0
�[2Klength 1
�[2Klength 2
�[2Klength 3
�[2Klength 4
�[2Klength 5
�[2Klength 6
�[2Klength 7
�[2Klength 8
�[2Klength 9
�[2Klength 10
�[2Klength 11
�[2Klength 12
�[2Klength 13/ 3844)
�[2Klength 14 / 3844)
37.8 % (1452�[2KPassword: NS1kxZf8uLDA†Î / 3844)
^C.8 % (1453 / 3844)
time
The current time is: 22.01.53,37

Old output:
https://forum.xda-developers.com/t/file-encrypted-how-can-i-open-it-help.4194779/post-85091353

[kimci86]

Thank you @cxzstuff for your feedback.

Output a bit messy

I just added a workaround to have a cleaner output. I should also add a protection not to print progress and a password at the same time.

Found it and continued. At 1452 instead of 1455/3844 like before.

The exact order in which passwords are tested can vary a little so this is normal.

That starting point option would help a lot

I agree! I am working on it. Should be ready by the end of next week at the latest.

[kimci86]

With the last change, you can restart a password recovery stopped either because a password was found and exhaustive mode was disabled or because the program was stopped by the user (by pressing Ctrl + C or Ctrl + Shift + C). The starting point is printed before exiting.
I need to make it more precise and clean up the implementation but it can already be used to save time.

[cxzstuff]

You're quick. Works quite nicely.
bkcrack -k 6eda3a27 2edfbde4 237a1e01 -r 20 ?a -e -s 16840
gives the password right away.
If copied as in powershell/cmd window it's: "NS1kxZf8uLDAå╬"
Instead of of the right one: "NS1kxZf8uLDA†Î "
So outputting it/log into a text file could be a good enhancement.

edit: okay changing code page to "ANSI Latin 1; Western European (Windows)" fixed it in my case.
That is chcp 1252. But still a log would be great. In case of power cut for example.
Like once in a minute or so... or what is suitable.

[kimci86]

This was too old, I started over.
See #100