Hi Goatpig, thanks for taking the time to reply and all your work within the community!
Please see my answers bellow :
And I'm guessing no paper backup?
That's correct, unfortunately.
This stuff supports Armory? Have you tested it? (i.e. create a wallet, give it to btcrecover with 1-2 characters off of the password and see if it can figure it out)
Yes it does support it, I gave it a try with a wallet created on version 93.3 and 0.85, both worked and were able to find the test password I created. Also, I figured out that some Armory versions have different unlock times and results in much faster attempt at bruteforcing.
Please see test results here : C:\btcrecover-master>btcrecover.py --wallet armory_2ZeUsv9ZR_.wallet --tokenlist tokens4.txt --enable-gpu --global-ws 600 --typos-case
Starting btcrecover 0.17.10 on Python 2.7.7 64-bit, 16-bit unicodes, 32-bit ints
btcrecover.py: warning: --typos COUNT not specified; assuming 1
Usage: btcrecover.py [options]
btcrecover.py: error: no such option: --language
btcrecover.py: warning: each --global-ws should probably be divisible by 32 for good performance
Wallet difficulty: 8 MiB, 3 iterations + ECC
Using OpenCL GPU GeForce RTX 2060
2376 of 2830 [##################################-------] 0:00:19, ETA: 0:00:03
Password found: 'Test1234$'The tokens4.txt file only contains the following :+ test :
means the word test is anywhere in the password. Combined with typos-case, it tests uppercase for all letters in possible combinations+ 1234 :
means 1234 is anywhere in the password%p :
means any possible ASCII charactersSame test applies.
Will do!
The fragmented backup vulnerability doesn't erode the security that much. It messes up the SSS setup but there is no real world attack against that. This is all theoretical. The recommendation I stickied here was for people using SSS to proactively redo their backups with the fixed implementation.
At any rate, to even begin exploring this angle, it would mean you have a set of fragmented paper backups. If that's the case, you don't have to crack anything in the first place.
Thank you for the detailed answer, didn't know the fragmented paper backup was a prerequisite. Can't go this path indeed.
Once you've established that the bruteforce software you're using actually works on these specific Armory wallets, you can start building a strategy to brute force whatever you remember. If you use a typical pattern across all your passwords or use a password manager, that can be useful too. First ensure you aren't wasting energy getting false negatives.
Right, since I know the btcrecover is working fine, I guess my best bet is to put more energy in bruteforcing the list of passwords. Yes I have a pattern accross my passwords and I was using a password manager, what can be useful about it?
Do you know perhaps, where I could find version 0.88.1?
Thank you,
Show Posts
