|
alumar (OP)
|
 |
January 16, 2014, 04:58:34 AM |
|
a old bitcoin 0.2 client with a wallet.dat that you remember running for a strong 6 months...
You may have a basic idea what the encryption password is, but what you have tried hasnt worked, but could of used only a combination of about 12 different things. Brute force ... could take months?
|
|
|
|
charleshoskinson
Legendary
 Offline
Activity: 1134
Merit: 1008
CEO of IOHK
|
|
January 16, 2014, 05:22:57 AM |
|
How many coins we taking about here?
|
The revolution begins with the mind and ends with the heart. Knowledge for all, accessible to all and shared by all
|
|
|
|
Keyser Soze
|
|
January 16, 2014, 05:32:08 AM |
|
You'd have to look around the forum a bit, but there's at least a couple people out there offering password cracking services. Success rate would depend on how much of the password you remember, complexity and so forth. I believe there is also a way to do this without exposing the private keys to the person, if they are successful.
|
|
|
|
|
|
alumar (OP)
|
|
January 16, 2014, 05:33:12 AM |
|
absolutely no clue, pc is a old dell d530 with a Intel QuadCore Q6600 ... so in that time, was a pretty nice processor to grind bitcoins, it also had a 4870 ...but from memory ... i dont remember doing GPU mining.
|
|
|
|
phillipsjk
Legendary
Offline
Activity: 1008
Merit: 1001
Let the chips fall where they may.
|
|
January 16, 2014, 06:06:00 AM
Last edit: January 26, 2014, 06:22:13 PM by phillipsjk |
|
I locked myself out of my own wallet. I think I recall choosing the length such that I can likely brute-force in the next 40 years (about 72 bits96 bits of entropy). I have it written down, so actual typos should be testable within a day.
I am thinking eventually wallets should start to integrate a "crack the password" feature. Though that would not work for extremely long/high-quality passphrases.
OP: I recommend backing up your wallet. Would suck if you crack the password, only to learn the drive crapped out.
|
James' OpenPGP public key fingerprint: EB14 9E5B F80C 1F2D 3EBE 0A2F B3DE 81FF 7B9D 5160 |
|
|
|
bennybong
|
|
January 16, 2014, 06:43:52 AM |
|
Just keep trying man. This happened to me once. The password is in your head somewhere... Just don't drive yourself too mad! And make/upload a backup somewhere safe & secure asap.
Good luck! I hope you and your bitcoins are reunited some day.
|
|
|
|
|
mikewoods
Newbie
Offline
Activity: 50
Merit: 0
|
|
January 16, 2014, 06:55:47 AM |
|
Just start writing any passwords hints down.
I had similar problem and I ended up building program that generated all possible passwords based on hints I had - few hundreds of those - which ended up containing the correct one.
|
|
|
|
|
grue
Legendary
Offline
Activity: 2058
Merit: 1431
|
|
January 16, 2014, 03:54:51 PM |
|
0.2 didn't have encryption. That was added in 0.6.0
|
|
|
|
deepceleron
Legendary
Offline
Activity: 1512
Merit: 1032
|
|
January 16, 2014, 07:53:22 PM |
|
0.2 didn't have encryption. That was added in 0.6.0
0.4.0. Worked securely in 0.5.0. |
|
|
|
|
|
bennybong
|
|
January 17, 2014, 03:36:08 AM |
|
0.2 didn't have encryption. That was added in 0.6.0
On snap. OP? Your not going to tell this was just hypothetical all along are you...  |
|
|
|
|
|
empoweoqwj
|
|
January 17, 2014, 04:28:34 AM |
|
0.2 didn't have encryption. That was added in 0.6.0
On snap. OP? Your not going to tell this was just hypothetical all along are you... Well "Hypothetical" is in the title  or did he add that after  |
|
|
|
|
|
