Its wireless with a receiver on top of the PC. Sometimes if your not sat in the correct position or the receiver has moved you can type a sentence and it wont pick certain keys up for example I may have thought I entered my password as:
123456789
but what you have actually typed will be
1245679
There is a good chance that this would have happened twice as well, It also does it sometimes if the battery is running low.
I guess I'm just trying to narrow down what mistake I made when I entered the password, and therefore narrow down the search the scrypt needs to follow
Topic: Encrypted wallet.dat, lost password, any solutions? - page 17. (Read 213559 times)
No not yet but it has only been running for a couple of hours I will leave it running for as long as needs be.
Would that list of possible passwords be as high if it was only searching for those missing 3? i.e not searching for 1 extra character or adjacent characters etc all at the same time?
It would still be very, very high, but yeah, if you're sure that adding/deleting/swapping characters isn't the problem, I guess you could remove those parts from the brute.rb script.Would that list of possible passwords be as high if it was only searching for those missing 3? i.e not searching for 1 extra character or adjacent characters etc all at the same time?
I'm afraid I'm not competent in Ruby (my programming background is very different) so I couldn't program the script for you.
Could you explain more clearly what you mean about the wireless keyboard? Do you think you entered the password wrongly when you initially entered it to encrypt the wallet? You have to type it twice, so it's unlikely that a hardware error would result in an unintended password.
No not yet but it has only been running for a couple of hours I will leave it running for as long as needs be.
Would that list of possible passwords be as high if it was only searching for those missing 3? i.e not searching for 1 extra character or adjacent characters etc all at the same time?
Would that list of possible passwords be as high if it was only searching for those missing 3? i.e not searching for 1 extra character or adjacent characters etc all at the same time?
Did the version you have running on your test wallet manage to find the password?
Yes!Would anyone happen to know what I would change in the scrypt below so that it would check for between 1 and up to 3 missing characters?
The reason I'm thinking this may be the problem is, I'm using a wireless keyboard and sometimes when typing if your sat in the wrong place the keystrokes aren't always picked up.
# delete one char
passphrase.length.times do |i|
testphrase = passphrase.dup
testphrase = testphrase[0,i] + testphrase[(i+1)..-1]
list << testphrase
end
Thanks
Checking for three missing characters will force the program to try an almost incomprehensibly high number of solutions, since those characters could appear anywhere in the password. Even if such a script exists, I think you'd be looking at several months of constant bruteforcing before it found a password.The reason I'm thinking this may be the problem is, I'm using a wireless keyboard and sometimes when typing if your sat in the wrong place the keystrokes aren't always picked up.
# delete one char
passphrase.length.times do |i|
testphrase = passphrase.dup
testphrase = testphrase[0,i] + testphrase[(i+1)..-1]
list << testphrase
end
Thanks
Did it try all combinations for your password?
Would anyone happen to know what I would change in the scrypt below so that it would check for between 1 and up to 3 missing characters?
The reason I'm thinking this may be the problem is, I'm using a wireless keyboard and sometimes when typing if your sat in the wrong place the keystrokes aren't always picked up.
# delete one char
passphrase.length.times do |i|
testphrase = passphrase.dup
testphrase = testphrase[0,i] + testphrase[(i+1)..-1]
list << testphrase
end
Thanks
The reason I'm thinking this may be the problem is, I'm using a wireless keyboard and sometimes when typing if your sat in the wrong place the keystrokes aren't always picked up.
# delete one char
passphrase.length.times do |i|
testphrase = passphrase.dup
testphrase = testphrase[0,i] + testphrase[(i+1)..-1]
list << testphrase
end
Thanks
No problem! Very excited to find out if this works, keep me updated!
Will do at the moment i am doing all this on an old media center pc...
i3 dual core, just had a quick google and it seems high powered graphics carsd are the best
If i moved this over to a pc with a 7990 in it would the 7990 card automatically do the cracking instead of the cpu
Using resource monitor my 3570K i5 at 4.0Ghz is only using 20%-25% not sure if there is a way to increase this let me know if you find anything
No problem! Very excited to find out if this works, keep me updated!
Hi and thanks for all your work so far.
I've just managed to get this up and running so will see how it goes. I feel I may have to mess with some of the parameters in the scrypt but will leave it running for a while you never know.
Did the version you have running on your test wallet manage to find the password?
No problem! Very excited to find out if this works, keep me updated!
Will do at the moment i am doing all this on an old media center pc...
i3 dual core, just had a quick google and it seems high powered graphics carsd are the best
If i moved this over to a pc with a 7990 in it would the 7990 card automatically do the cracking instead of the cpu
No problem! Very excited to find out if this works, keep me updated!
Did you create the bitcoin.conf file in your wallet directory? That's the file that sets the RPC username and password. You can just copy the "raw data" part at the bottom of this page into Notepad and save it as "bitcoin.conf" in your wallet directory (the one that's C:\Users\
Yep looks like it's working!
Thanks again!
Did you create the bitcoin.conf file in your wallet directory? That's the file that sets the RPC username and password. You can just copy the "raw data" part at the bottom of this page into Notepad and save it as "bitcoin.conf" in your wallet directory (the one that's C:\Users\
Navigate (using the "cd" command I explained earlier) to C:\Program Files (x86)\Bitcoin\daemon (or on 32-bit Windows, that's just C:\Program Files\Bitcoin\daemon). You should be able to run bitcoind from there without any issues.
Thanks done that and got this error message
incorrect rcpuser or rcpassword
Navigate (using the "cd" command I explained earlier) to C:\Program Files (x86)\Bitcoin\daemon (or on 32-bit Windows, that's just C:\Program Files\Bitcoin\daemon). You should be able to run bitcoind from there without any issues.
Since neither Feathercoin nor Protoshares seem to have their own daemon versions, or even accept an argument to make them run as daemons, I've been trying to use bitcoind.exe to crack them.
Here's my method so far - somebody can correct me if there's an easier way:
1. Go to the folder where your bitcoin wallet is contained, and rename your wallet.dat file to something else (I used BITCOIN-wallet.dat - this is only temporary)
2. Copy in your wallet.dat file for the other currency (FTC/PTS), keeping its name as wallet.dat.
3. Create a new file called bitcoin.conf in the folder where your bitcoin wallet was contained (mine is C:\Users\\AppData\Roaming\Bitcoin). Click here for a copy of my bitcoin.conf, which is the Bitcoin wiki's "example" of a bitcoin.conf file, with the relevant lines uncommented. (The RPC username in my version is "hello1"; the RPC password is "hello2".)
3. Open command prompt. Navigate to a folder containing bitcoind.exe and launch it with the following parameters:
4. Leave this command prompt window open, and open another command prompt window. Navigate to a folder containing bitcoind.exe (yes, again) and type
If you get information, instead of an error, your bitcoind server is accessible via RPC. If you get an error, post what you did and I can try and fix it. 
5. Leaving both command prompts open, open "Start Command Prompt with Ruby", navigate to the location of brute.rb, and type
Let me know how this goes for you guys!
Here's my method so far - somebody can correct me if there's an easier way:
1. Go to the folder where your bitcoin wallet is contained, and rename your wallet.dat file to something else (I used BITCOIN-wallet.dat - this is only temporary)
2. Copy in your wallet.dat file for the other currency (FTC/PTS), keeping its name as wallet.dat.
3. Create a new file called bitcoin.conf in the folder where your bitcoin wallet was contained (mine is C:\Users\
3. Open command prompt. Navigate to a folder containing bitcoind.exe and launch it with the following parameters:
Code:
bitcoind -server -daemon -rpcuser=hello1 -rpcpassword=hello2 -rpcport=8332
Code:
bitcoind getinfo
5. Leaving both command prompts open, open "Start Command Prompt with Ruby", navigate to the location of brute.rb, and type
Code:
ruby brute.rb
Let me know how this goes for you guys!
I will try this in the morning and let you know how I get on. Thanks for your help so far
Thanks again when i type bitcoind -server -daemon -rpcuser=hello1 -rpcpassword=hello2 -rpcport=8332
I get the error message "is not recognised etc etc"
Oh, here's a link to the version of brute.rb that worked for me. It's currently cycling through the different combinations and seems to be working fine; I've encrypted my (empty) test wallet with the passphrase "hello1" and I'm pretty sure it'll work it out in the end 
The only part you have to change is the "hello" at the top of the script, which you replace with your best guess at your password.
I believe you can also edit the list of characters:
So you can remove some of the punctuation, for example, if you're certain you didn't use it in your password.
Screenshot of my command prompt running through combinations:
The only part you have to change is the "hello" at the top of the script, which you replace with your best guess at your password.
I believe you can also edit the list of characters:
Code:
characters = " !\"\#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\\]^_`abcdefghijklmnopqrstuvwxyz{|}~"
list = []Screenshot of my command prompt running through combinations:
You first need to run your wallet in server mode from the CMD window
Once the wallet opens you type brute.rb and then it will try to open another version of your wallet.
If you keep closing the windows error pop up it will try another version of your password and the error window will pop up again, rinse and repeat
I gave up after about 2 hours was far to slow and I wasn't even sure it was trying the passwords
I'm thinking of going with the wallet recovery service see if they have any luck, only problem is they charge 20% of your wallet
Once the wallet opens you type brute.rb and then it will try to open another version of your wallet.
If you keep closing the windows error pop up it will try another version of your password and the error window will pop up again, rinse and repeat
I gave up after about 2 hours was far to slow and I wasn't even sure it was trying the passwords
I'm thinking of going with the wallet recovery service see if they have any luck, only problem is they charge 20% of your wallet
So you get that error message cannot contain lock on directory etc and then you have to keep on clicking ok...
No problem! In all honesty, I'm interested because of the bounty, but researching this is teaching me all kinds of things I didn't know about wallet encryption, so I'm enjoying helping you two.
Since neither Feathercoin nor Protoshares seem to have their own daemon versions, or even accept an argument to make them run as daemons, I've been trying to use bitcoind.exe to crack them.
Here's my method so far - somebody can correct me if there's an easier way:
1. Go to the folder where your bitcoin wallet is contained, and rename your wallet.dat file to something else (I used BITCOIN-wallet.dat - this is only temporary)
2. Copy in your wallet.dat file for the other currency (FTC/PTS), keeping its name as wallet.dat.
3. Create a new file called bitcoin.conf in the folder where your bitcoin wallet was contained (mine is C:\Users\\AppData\Roaming\Bitcoin). Click here for a copy of my bitcoin.conf, which is the Bitcoin wiki's "example" of a bitcoin.conf file, with the relevant lines uncommented. (The RPC username in my version is "hello1"; the RPC password is "hello2".)
3. Open command prompt. Navigate to a folder containing bitcoind.exe and launch it with the following parameters:
4. Leave this command prompt window open, and open another command prompt window. Navigate to a folder containing bitcoind.exe (yes, again) and type
If you get information, instead of an error, your bitcoind server is accessible via RPC. If you get an error, post what you did and I can try and fix it.
5. Leaving both command prompts open, open "Start Command Prompt with Ruby", navigate to the location of brute.rb, and type
Let me know how this goes for you guys!
Here's my method so far - somebody can correct me if there's an easier way:
1. Go to the folder where your bitcoin wallet is contained, and rename your wallet.dat file to something else (I used BITCOIN-wallet.dat - this is only temporary)
2. Copy in your wallet.dat file for the other currency (FTC/PTS), keeping its name as wallet.dat.
3. Create a new file called bitcoin.conf in the folder where your bitcoin wallet was contained (mine is C:\Users\
3. Open command prompt. Navigate to a folder containing bitcoind.exe and launch it with the following parameters:
Code:
bitcoind -server -daemon -rpcuser=hello1 -rpcpassword=hello2 -rpcport=8332
Code:
bitcoind getinfo
5. Leaving both command prompts open, open "Start Command Prompt with Ruby", navigate to the location of brute.rb, and type
Code:
ruby brute.rb
Let me know how this goes for you guys!
I will try this in the morning and let you know how I get on. Thanks for your help so far
Since neither Feathercoin nor Protoshares seem to have their own daemon versions, or even accept an argument to make them run as daemons, I've been trying to use bitcoind.exe to crack them.
Here's my method so far - somebody can correct me if there's an easier way:
1. Go to the folder where your bitcoin wallet is contained, and rename your wallet.dat file to something else (I used BITCOIN-wallet.dat - this is only temporary)
2. Copy in your wallet.dat file for the other currency (FTC/PTS), keeping its name as wallet.dat.
3. Create a new file called bitcoin.conf in the folder where your bitcoin wallet was contained (mine is C:\Users\\AppData\Roaming\Bitcoin). Click here for a copy of my bitcoin.conf, which is the Bitcoin wiki's "example" of a bitcoin.conf file, with the relevant lines uncommented. (The RPC username in my version is "hello1"; the RPC password is "hello2".)
3. Open command prompt. Navigate to a folder containing bitcoind.exe and launch it with the following parameters:
If you enter this correctly, the title of the command prompt window should permanently change and you won't be able to type anything anymore.
4. Leave this command prompt window open, and open another command prompt window. Navigate to a folder containing bitcoind.exe (yes, again) and type
If you get information (screenshot), instead of an error, your bitcoind server is accessible via RPC. If you get an error, post what you did and I can try and fix it.
5. Leaving both command prompts open, open "Start Command Prompt with Ruby", navigate to the location of brute.rb, and type
Let me know how this goes for you guys!
EDIT: if step 4 brings up an error saying "couldn't connect to server", just try the command again, and again, and again. When it happened to me, I just left the server on for about 15 minutes, then tried it and it worked.
Here's my method so far - somebody can correct me if there's an easier way:
1. Go to the folder where your bitcoin wallet is contained, and rename your wallet.dat file to something else (I used BITCOIN-wallet.dat - this is only temporary)
2. Copy in your wallet.dat file for the other currency (FTC/PTS), keeping its name as wallet.dat.
3. Create a new file called bitcoin.conf in the folder where your bitcoin wallet was contained (mine is C:\Users\
3. Open command prompt. Navigate to a folder containing bitcoind.exe and launch it with the following parameters:
Code:
bitcoind -server -daemon -rpcuser=hello1 -rpcpassword=hello2 -rpcport=8332
4. Leave this command prompt window open, and open another command prompt window. Navigate to a folder containing bitcoind.exe (yes, again) and type
Code:
bitcoind getinfo
5. Leaving both command prompts open, open "Start Command Prompt with Ruby", navigate to the location of brute.rb, and type
Code:
ruby brute.rb
Let me know how this goes for you guys!
EDIT: if step 4 brings up an error saying "couldn't connect to server", just try the command again, and again, and again. When it happened to me, I just left the server on for about 15 minutes, then tried it and it worked.
You first need to run your wallet in server mode from the CMD window
Once the wallet opens you type brute.rb and then it will try to open another version of your wallet.
If you keep closing the windows error pop up it will try another version of your password and the error window will pop up again, rinse and repeat
I gave up after about 2 hours was far to slow and I wasn't even sure it was trying the passwords
I'm thinking of going with the wallet recovery service see if they have any luck, only problem is they charge 20% of your wallet
Once the wallet opens you type brute.rb and then it will try to open another version of your wallet.
If you keep closing the windows error pop up it will try another version of your password and the error window will pop up again, rinse and repeat
I gave up after about 2 hours was far to slow and I wasn't even sure it was trying the passwords
I'm thinking of going with the wallet recovery service see if they have any luck, only problem is they charge 20% of your wallet
Jump to: