Encrypted wallet.dat, lost password, any solutions?

[clochard]

So, given that my old password is correct (which I am quite quite certain about), these would be the steps to follow?

1: Deinstalling current bitcoin client
2: Removing all data, blocks, and current wallet.dat
3: Downloading new Bitcoin client
4: Removing wallet.dat new bitcoin client
5: Inserting old wallet.dat in the folder where the new wallet.dat was located
6: Open command: "bitcoin-qt.exe -rescan"
7: Let the client rescan all the blocks and once it is finished, I should be able to make transfers with my old password

Am I correct here on these steps?

Best,

Clochard

[telepatheic]

So, given that my old password is correct (which I am quite quite certain about), these would be the steps to follow?

1: Deinstalling current bitcoin client
2: Removing all data, blocks, and current wallet.dat
3: Downloading new Bitcoin client
4: Removing wallet.dat new bitcoin client
5: Inserting old wallet.dat in the folder where the new wallet.dat was located
6: Open command: "bitcoin-qt.exe -rescan"
7: Let the client rescan all the blocks and once it is finished, I should be able to make transfers with my old password

Am I correct here on these steps?

Best,

Clochard

No need to remove all data and blocks. Other than that those are the right steps.

[clochard]

The problem is, again, that when I only remove the wallet.dat file and I insert the old wallet.dat backed up file, it still states the password is wrong.

When I am completely certain the password is correct...

[telepatheic]

The problem is, again, that when I only remove the wallet.dat file and I insert the old wallet.dat backed up file, it still states the password is wrong.

When I am completely certain the password is correct...

I can't work out what is wrong then. Try using btcrecover https://github.com/gurnec/btcrecover

If that doesn't work, your file has probably become corrupted and you will need an expert to have a look at it and see if it can be repaired.

[clochard]

I reinstalled the entire Bitcoin client, removed the new wallet.dat, introduced the backed up wallet.dat and opened the client. I can see my transactions but I cannot see saldo (probably after synchronizing) and I can still not change my password.

How the hell is that possible??

I have 1000% sure the correct password, I copy it from notepad into the field and it keeps repeating me it is incorrect.

Is there any way that the file has become corrupted or the password has changed?

And if I would manage to restart my old computer, would I be able to open my wallet there? The last time I tried to open my wallet there I got a system error: corrupt database

Anyone here that can help me out? It starts to stress me

Many thanks!!

Clochard

[clochard]

I have been thinking it over and over and I came up with an idea what could be the cause (there is a small chance it is like this, but I cannot rule it out).

The keyboard of my old computer was sometimes malfunctioning, e.g. letters that did not appear on the screen despite hitting them.

Could it have been, that one or two letters continuously were not hit, while I thought I typed them and therefore wrote down on paper another password then I typed?

That could explain something. The shitty thing is, I later destroyed my keyboard when I trew over a glass of water, so now trying to get that computer to work and retype the password there is not going to work.

If however this is the case, bruteforcing it might help. But still, in my attempt to create a safe password I created a phrase of around 35 letters and numbers , so I am not sure how feasible it is to crack it...

In the mean time, I will keep looking for solutions. Any insight or advice is highly appreciated!

Best,

Clochard

[DannyHamilton]

- snip -

The keyboard of my old computer was sometimes malfunctioning, e.g. letters that did not appear on the screen despite hitting them.

Could it have been, that one or two letters continuously were not hit, while I thought I typed them and therefore wrote down on paper another password then I typed?

- snip -

If however this is the case, bruteforcing it might help. But still, in my attempt to create a safe password I created a phrase of around 35 letters and numbers , so I am not sure how feasible it is to crack it...

- snip -

If you're just looking for a few missing characters in an otherwise exact password, it wouldn't be difficult to write a computer program that could try all possibilities. The program shouldn't take long at all to try them all and report back to you if any of them worked.

[telepatheic]

If you're just looking for a few missing characters in an otherwise exact password, it wouldn't be difficult to write a computer program that could try all possibilities. The program shouldn't take long at all to try them all and report back to you if any of them worked.

The program already exists: btcrecover. Use the

Code:

--typos-delete 

feature to test all deleted character possibilities.

[clochard]

Cool thanks, that might be an option to try!

First thing I will do now this weekend is to take out the hard disk of my old computer and connect it to another computer and see if I can launch the Bitcoin client from there and if there my password still works.

If not, I will take other steps such as the password recovery tool.

Just in case I am completely confused, I already wrote down the password  I think it is (pretty certain about it) plus some extra words and combinations I tend to use in other passwords, so I can try many possibilities.

I keep you updated about the process! Many thanks!

Best,

Clochard

[Stan-O]

here's one that is probably very easy to figure out.  i know the first 7 characters of the passphrase, and have some combination of 4-8 numbers on the end, no spaces anywhere.

i tried using this script, but i'm sure it's going about it the wrong way.  I made a myriadcoind and the script runs, but looks like it would take forever and a day to actually find the password.  lil help?   thanks.

Code:

#!/usr/bin/ruby -w

passphrase = "Abcdefg12345678"

def test(phrase)
  print phrase, "\t"
  system("./myriadcoind", "walletpassphrase", phrase, "20")
  case $?.exitstatus
  when 0
    puts "Found it!  #{phrase}"
    exit 0
  when 127
    puts "myriadcoind not found in current dir"
    exit 1
  end
end

def scramble(passphrase)
  characters = " !\"\#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\\]^_`abcdefghijklmnopqrstuvwxyz{|}~"
  list = []

  # transpose adjacent chars
  (passphrase.length - 1).times do |i|
    testphrase = passphrase.dup
    testphrase[i] = passphrase[i+1]
    testphrase[i+1] = passphrase[i]
    list << testphrase
  end

  # delete one char
  passphrase.length.times do |i|
    testphrase = passphrase.dup
    testphrase = testphrase[0,i] + testphrase[(i+1)..-1]
    list << testphrase
  end

  # substitutute one char
  passphrase.length.times do |i|
    characters.chars.each do |c|
      testphrase = passphrase.dup
      testphrase[i] = c
      list << testphrase
    end
  end

  # insert one char
  (passphrase.length + 1).times do |i|
    characters.chars.each do |c|
      testphrase = passphrase.dup
      testphrase.insert(i, c)
      list << testphrase
    end
  end

  return list.uniq
end

list1 = scramble(passphrase)
list1.each { |i| test i }
list1.each { |i| scramble(i).each { |j| test j }}

puts "No luck."
exit 1

[Revalin]

here's one that is probably very easy to figure out.  i know the first 7 characters of the passphrase, and have some combination of 4-8 numbers on the end, no spaces anywhere.

Start myraidcoind like this:

Code:

myriadcoind -rpcpass=some-password

Then run this script:

Code:

#!/usr/bin/ruby -w
require 'net/http'
require 'json'

start = "passphrase"
min_digits = 4
max_digits = 8

$rpc_user = ""
$rpc_pass = "some-password"
$rpc_port = 10889

def test(passphrase)
  puts passphrase.inspect
  request = Net::HTTP::Post.new("/")
  request.basic_auth $rpc_user, $rpc_pass
  request.body = { method:"walletpassphrase", params:[passphrase, 1] }.to_json
  response = Net::HTTP.new("localhost", $rpc_port).request(request)
  if response.code == "401" ; puts "Incorrect RPC user/pass" ; exit 1 ; end
  ret = JSON.parse response.body
  if ret["error"].nil? ; puts "\nFound it! #{passphrase.inspect}" ; exit ; end
  return if ret["error"]["code"] == -14 # wrong passphrase
  raise "WTF? #{ret.inspect}"
end

(min_digits..max_digits).each do |digits|
  (10**digits).times do |i|
    test("%s%0#{digits}d" % [start, i])
  end
end

puts "No luck."
exit 1

It'll take about 1 day for 6 digits, 2 weeks for 7, 3 months for 8.

[Revalin]

For everyone asking about Multibit: Sorry, I don't have time to write an interface for it right now.  If someone creates a command line or JSON-RPC API I can use to test a password I'll be happy to plug my script into it.

Here is the JSON-RPC for recovering Multibit passwords.
This in only for Multibit, i'm working on Armory as well.

https://dl.dropboxusercontent.com/u/71434563/rpc-service.jar

This is interesting, but I don't want to touch it unless I can build it myself.  Can you post the source?

[Stan-O]

here's one that is probably very easy to figure out.  i know the first 7 characters of the passphrase, and have some combination of 4-8 numbers on the end, no spaces anywhere.

Start myraidcoind like this:

Code:

myriadcoind -rpcpass=some-password

Then run this script:

Code:

#!/usr/bin/ruby -w
require 'net/http'
require 'json'

start = "passphrase"
min_digits = 4
max_digits = 8

$rpc_user = ""
$rpc_pass = "some-password"
$rpc_port = 10889

def test(passphrase)
  puts passphrase.inspect
  request = Net::HTTP::Post.new("/")
  request.basic_auth $rpc_user, $rpc_pass
  request.body = { method:"walletpassphrase", params:[passphrase, 1] }.to_json
  response = Net::HTTP.new("localhost", $rpc_port).request(request)
  if response.code == "401" ; puts "Incorrect RPC user/pass" ; exit 1 ; end
  ret = JSON.parse response.body
  if ret["error"].nil? ; puts "\nFound it! #{passphrase.inspect}" ; exit ; end
  return if ret["error"]["code"] == -14 # wrong passphrase
  raise "WTF? #{ret.inspect}"
end

(min_digits..max_digits).each do |digits|
  (10**digits).times do |i|
    test("%s%0#{digits}d" % [start, i])
  end
end

puts "No luck."
exit 1

It'll take about 1 day for 6 digits, 2 weeks for 7, 3 months for 8.

thanks Revalin.  i could swear it's 4 digits on the end.  

i'll give it a go and let you know how it turns out.

It's returning this error:

net/http: warning: Content-Type did not set; using application/x-www-form-urlenc
oded

and then a password attempt.  is it working?  it's runing through the passwords, but not sure if its actually applying them.

[clochard]

I just wanted to share that I fixed it. For god's sake.

I took out the hard disk of my old pc, connected it to another one and took the wallet.dat file. I then imported it into blockchain. It asked for my password, I typed the password that I knew was connected to that wallet.dat file but did not work in my new computer and it worked.

Thanks for all the tips!

Best,

Clochard

[Stan-O]

I just wanted to share that I fixed it. For god's sake.

I took out the hard disk of my old pc, connected it to another one and took the wallet.dat file. I then imported it into blockchain. It asked for my password, I typed the password that I knew was connected to that wallet.dat file but did not work in my new computer and it worked.

Thanks for all the tips!

Best,

Clochard

This got me to thinking.  I cloned my wallet VM a while back, and had been working off of the clone.   So, i shut down the clone, fired up the original, and there's my unencrypted MyriadCoin wallet.  imagine that!!  lol

thanks again Revalin for your help.  didn't need the script after all.

[Revalin]

net/http: warning: Content-Type did not set; using application/x-www-form-urlencoded

and then a password attempt.  is it working?  it's runing through the passwords, but not sure if its actually applying them.

Yes, that's fine.  The wallet doesn't care about the content-type.  If you want to see everything it's doing in detail then make this change (add the middle line):

Code:

  response = Net::HTTP.new("localhost", $rpc_port).request(request)
  puts request.body, response.body
  if response.code == "401" ; puts "Incorrect RPC user/pass" ; exit 1 ; end

[vauhoa]

Do you remember the day and hour the last time you had access to your BTC's?
Then I suggest you find a very good hypnotherapist that will recall all the information from your mind! javascript:void(0); If it works, don't forget me as I got Goxed!!! javascript:void(0); Best luck!!!

[steelbuzz]

Wow... It took you two years to fix this problem??? 

[paythrough_team]

Lost password is a troublesome thing, and God bless you.

[thiec]

Very nice thread. Mark it and i hope i wont visit here searching for my own mistake.