Author

Topic: Brute forcing wallet.dat? (Read 1280 times)

sr. member
Activity: 476
Merit: 283
February 21, 2017, 10:26:38 PM
#14
Well I mean random in that there was no pattern selected by me to generate the passphrase to help with brute forcing it.
legendary
Activity: 2128
Merit: 1073
February 21, 2017, 10:09:12 PM
#13
Had I not found my saved passphrase there is no way I would have been able to recover it. Unfortunately no amount of meditation would help me remember 24 completely random characters.
I don't want to discourage you, but I've been to long on this forum to take "completely random" at the face value. Too many people here thought that they have "random number generators", but the real entropy was significantly lower (e.g. under 15 or 31 bits). It has been a common problem and frequent reason of the thefts: it looked random but it wasn't.

Since you've admitted to using Excel I just hope that you didn't use the builtin functions to generate those "completely random characters". In fact, I wanted to encourage you to read this forum and re-check the source of your randomness. In the past people here discussed the flaws in various tools (commercial and free) that purport to generate random numbers.
sr. member
Activity: 476
Merit: 283
February 21, 2017, 08:14:00 PM
#12
Had I not found my saved passphrase there is no way I would have been able to recover it. Unfortunately no amount of meditation would help me remember 24 completely random characters. Even after I found it I needed the  btrecover tool to figure it out since the last character was incorrectly copied into the BTC client. I guess live and learn. Next time I'll be more careful with where I save my files and how I copy them. Thank god I take full backups of all my machines and keep them long term and there are some really smart people out there willing to help and create tools to help other people out.
legendary
Activity: 2128
Merit: 1073
February 21, 2017, 08:08:21 PM
#11
I don't understand is a line feed not a specific character?

EDIT: NVM I got it. Thank you so much guys for the help. I thought I was going to be sick but now I'm relived.
Yeah!

For password/pass-phrase recovery the key to success is the right frame of mind. In the original btc-recover thread somebody made a good post about how to meditate to get into that state of mind one had at the time of entering that password first time.

Microsoft Windows is particularly nasty with this regard because it is well known that the automatic driver updates may change the behavior of the keyboard/mouse/video card combination.
sr. member
Activity: 476
Merit: 283
February 21, 2017, 07:45:36 PM
#10
That makes sense. I believe I created the password in excel and copied it over to my BTC wallet but how do I enter this into the passphrase of my bitcoin client?
Only you can really answer your question. Some people cut and paste it directly to bitcoin-qt. Other cut and paste it to a command prompt window using "bitcoin-cli walletpassphrase ..." . It is a common problem for the users of non-US-English Windows that various things typed on the keyboard result in different characters feed to the program. Now that you mentioned a program from the Microsoft Office suite I'm also aware that those programs in particular are known for creating problems by automagically changing entered texts to make them look better: e.g. "smart quotes", auto ligatures (ffi, etc.) and other traps for unwary.


I don't understand is a line feed not a specific character?

EDIT: NVM I got it. Thank you so much guys for the help. I thought I was going to be sick but now I'm relived.
legendary
Activity: 2128
Merit: 1073
February 21, 2017, 07:32:53 PM
#9
That makes sense. I believe I created the password in excel and copied it over to my BTC wallet but how do I enter this into the passphrase of my bitcoin client?
Only you can really answer your question. Some people cut and paste it directly to bitcoin-qt. Other cut and paste it to a command prompt window using "bitcoin-cli walletpassphrase ..." . It is a common problem for the users of non-US-English Windows that various things typed on the keyboard result in different characters feed to the program. Now that you mentioned a program from the Microsoft Office suite I'm also aware that those programs in particular are known for creating problems by automagically changing entered texts to make them look better: e.g. "smart quotes", auto ligatures (ffi, etc.) and other traps for unwary.
sr. member
Activity: 476
Merit: 283
February 21, 2017, 07:19:44 PM
#8
The issues is it is indicated that a line return character was the missing character. How would that even be entered into the passphrase? Really appreciate any help!
That would be typically related to entering the pass-phrase from the keyboard vs cutting&pasting from a text editor vs entering it from command prompt/shell prompt. It also happens oftentimes when people work with several keyboard layouts and delay lifting the finger off the AltGr/Option key: the first Enter/Return gets ignored.

You may have also physically switched the keyboards between then and now and the new keyboard has different tactile feel, or maybe you cleaned or dirtied you keyboard. This problem mostly happen to the touch typists who don't look at the keyboard and/or screen when typing.

Once you really think about how you typed the pass-phrase you may probably find other variables that you originally didn't notice. I'm glad that you've learned this without paying the price for the lost data and/or coins.
 

That makes sense. I believe I created the password in excel and copied it over to my BTC wallet but how do I enter this into the passphrase of my bitcoin client?
legendary
Activity: 2128
Merit: 1073
February 21, 2017, 07:01:02 PM
#7
The issues is it is indicated that a line return character was the missing character. How would that even be entered into the passphrase? Really appreciate any help!
That would be typically related to entering the pass-phrase from the keyboard vs cutting&pasting from a text editor vs entering it from command prompt/shell prompt. It also happens oftentimes when people work with several keyboard layouts and delay lifting the finger off the AltGr/Option key: the first Enter/Return gets ignored.

You may have also physically switched the keyboards between then and now and the new keyboard has different tactile feel, or maybe you cleaned or dirtied you keyboard. This problem mostly happen to the touch typists who don't look at the keyboard and/or screen when typing.

Once you really think about how you typed the pass-phrase you may probably find other variables that you originally didn't notice. I'm glad that you've learned this without paying the price for the lost data and/or coins.
 
sr. member
Activity: 476
Merit: 283
February 21, 2017, 06:06:46 PM
#6
Ok so dug really deep and I was able to find my password on an old system backup (thank god). However when I try to use it it says its incorrect. So I then ran the password through btrecover with the password I found and a %P wildcard at the end. It said it found the password. The issues is it is indicated that a line return character was the missing character. How would that even be entered into the passphrase? Really appreciate any help!
legendary
Activity: 3472
Merit: 4801
February 21, 2017, 04:36:48 PM
#5
With a random string of 25 characters, it is incredibly unlikely that you will be able to brute force your wallet. In fact, it is basically impossible. Unfortunately your Bitcoin is now lost.

I do believe it was only numbers and lowercase letters. Does that make it any more likely?

36 possible characters for each of 25 positions.

3625 = 808281277464764060643139600456536293376

That's 8.08 X 1038

Lets assume you can try a billion passwords per second.
In that case it will take you 1.28 X 1022 YEARS to try HALF of the possible passwords.  At that point you'll have only a 50% chance of having stumbled across the right password.

The more you can remember, the better your chances get.

Any letters or numbers that you are certain aren't in the password?
Any letters or numbers that you are certain are in the password?
Are you certain whether the first character was a letter or number?
How about the second character (letter vs number)?
The last character?

staff
Activity: 3458
Merit: 6793
Just writing some code
February 21, 2017, 03:45:14 PM
#4
With a random string of 25 characters, it is incredibly unlikely that you will be able to brute force your wallet. In fact, it is basically impossible. Unfortunately your Bitcoin is now lost.

I do believe it was only numbers and lowercase letters. Does that make it any more likely?
Still extremely unlikely given the length of the password.
sr. member
Activity: 476
Merit: 283
February 21, 2017, 03:36:03 PM
#3
With a random string of 25 characters, it is incredibly unlikely that you will be able to brute force your wallet. In fact, it is basically impossible. Unfortunately your Bitcoin is now lost.

I do believe it was only numbers and lowercase letters. Does that make it any more likely?
staff
Activity: 3458
Merit: 6793
Just writing some code
February 21, 2017, 03:29:56 PM
#2
With a random string of 25 characters, it is incredibly unlikely that you will be able to brute force your wallet. In fact, it is basically impossible. Unfortunately your Bitcoin is now lost.
sr. member
Activity: 476
Merit: 283
February 21, 2017, 03:20:44 PM
#1
So as would appear to be my stupidity I seem to have lost the passphrase to unlock my bitcoin wallet. I thought I had had it backed up but it would appear not Sad I have plenty of backups of my wallet but they are all locked. I also have the log file from when the wallet was encrypted. I looked into unlocking it with some of the recovery tools but I believe I used a random string of characters with no "passphrase" My question is is it possible (please I hope so) to brute force the password. I believe the password is around 25 characters long. I don't care if it would take a long time to determine. I have a server I can dedicate to this task full time with 24 threads available to help brute force the password. Someone give me some good news please Sad
Jump to: