can't access encrypted wallet.dat - looking for ideas (SOLVED!)

[tjc]

I created an offline wallet in 7/13 based on this workflow https://en.bitcoin.it/wiki/How_to_set_up_a_secure_offline_savings_wallet.

I recently imported the encrypted wallet.dat file into the bitcoin-qt wallet on Windows 7. Coins appeared.

But, I my recorded passphrase is incorrect. At first I though I mis-recorded it or mis-typed it at inception. I have contacted a service to try to brute force it.

However, I just went to restore and access my offline LTC wallet and same thing. Coins appear but passphrase is wrong.

Same mistake twice seems pretty unlikely. Is there any other mistake I could have made that led to this? Please help me brainstorm.

Thanks

[Zae]

Try capslock.

[gerXhonza]

Maybe different keyboard language when you have localized version of OS

[niothor]

Try capslock.

Either this or try opening a notepad and type your password 10 times , see if you're doing a mistake.
Also broken keyboard

[tjc]

Yes, I tried capslock in addition to about 500 iterations of the password. I am looking for ideas for mistakes other than password typing errors.

Thanks

Maybe different keyboard language when you have localized version of OS

Interesting, I created the wallet and did the encryption on a Ubuntu 12.01 live CD on an old laptop. I still have the CD and laptop. I'll install it, reload the wallet.dat and try the passphrase.

Thanks

[tjc]

Still not working with original OS and laptop.

Appreciate any and all ideas.

Thanks

[Scottie]

Yes, I tried capslock in addition to about 500 iterations of the password. I am looking for ideas for mistakes other than password typing errors.

Thanks

Maybe different keyboard language when you have localized version of OS

Interesting, I created the wallet and did the encryption on a Ubuntu 12.01 live CD on an old laptop. I still have the CD and laptop. I'll install it, reload the wallet.dat and try the passphrase.

Thanks

Maybe try num lock as well?

[impulsee]

Really, Maybe NumLock/Caps Lock or another language?

[tjc]

Thanks for the ideas. I gave caplock and numlock a try again. Still no luck.

By the way, I learned I should have printed the private keys when creating the wallet. That way I could recover if there was a passphrase problem. Just wanted to pass that on for anyone who is not aware of that - like I was.

[sadycz]

what do you mean print them, im copy paste it from my pass doc... shall i be concerned?

[Kluge]

Since it seems to be something very slightly off, at least the brute-forcing should be relatively quick. No idea what the issue could be aside from what was already suggested outside of something stupid-obvious, like mistaking a "0" for a "O."

what do you mean print them, im copy paste it from my pass doc... shall i be concerned?

Both wallets and private keys can be printed. Private keys provide access to individual public keys. Wallets are the collection of private and public keys. AFAIK, there is not currently an easy way to print off encrypted private keys, so you should keep in mind it's much less secure (except in cases where you need to protect against yourself).

[tjc]

Since it seems to be something very slightly off, at least the brute-forcing should be relatively quick. No idea what the issue could be aside from what was already suggested outside of something stupid-obvious, like mistaking a "0" for a "O."

what do you mean print them, im copy paste it from my pass doc... shall i be concerned?

Both wallets and private keys can be printed. Private keys provide access to individual public keys. Wallets are the collection of private and public keys. AFAIK, there is not currently an easy way to print off encrypted private keys, so you should keep in mind it's much less secure (except in cases where you need to protect against yourself).

Yes I am thinking of way to protect against my self.

So, as follow up I was able to "brute force it". I used the Ruby script from this thread https://bitcointalk.org/index.php?topic=85495.300 posted by Revalin. See my post #312 for all the details.

Very grateful to everyone who helped me think this through.

[Zae]

Nice work!

I have contacted a service to try to brute force it.

If you have sent your wallet.dat with information to a 3rd party. please create a new wallet and transfer your funds.

[Kluge]

Since it seems to be something very slightly off, at least the brute-forcing should be relatively quick. No idea what the issue could be aside from what was already suggested outside of something stupid-obvious, like mistaking a "0" for a "O."

what do you mean print them, im copy paste it from my pass doc... shall i be concerned?

Both wallets and private keys can be printed. Private keys provide access to individual public keys. Wallets are the collection of private and public keys. AFAIK, there is not currently an easy way to print off encrypted private keys, so you should keep in mind it's much less secure (except in cases where you need to protect against yourself).

Yes I am thinking of way to protect against my self.

So, as follow up I was able to "brute force it". I used the Ruby script from this thread https://bitcointalk.org/index.php?topic=85495.300 posted by Revalin. See my post #312 for all the details.

Very grateful to everyone who helped me think this through.

There can be no closure until you satisfy our curiosity. What was the mistake?

[tjc]

Nice work!

I have contacted a service to try to brute force it.

If you have sent your wallet.dat with information to a 3rd party. please create a new wallet and transfer your funds.

Once I found the right passphrase I sent to another address within 10 seconds

So the mistakes are all user errors (me). There are two passcodes involved. One for a bitcoin wallet and one for litecoin. I created these both on the same day in July 2013. I found my original notes on paper today at work (after of course, I had found the correct passphrases using the Ruby script).

For BTC, the actual passphrase was d5VcQG+Rp8EqJ!x+Zsb. I had recorded in my notes and in my documentation as d5VckQG+Rp8EqJ!x+Zsb. My theory is either I omitted the k twice or the k was working inconsistently on the laptop I used. In trying to figure out the passphrase I tried omitting characters but in my haste (stressed state) I must not have been complete. 27 btc recovered.

For LTC, the actual passphrase was hMH#8vB2SqjCZdV&!6d9. I have that exact passphrase hand written in my notes I found at work today but in my documentation I recorded hMV#8vB2SqjCZdV&!6d9 substituting V for H. This must have been a problem transcribing from my notes to my documentation I kept with the wallet.dat files. 485 ltc recovered.

I have learned that in long random strings of characters, I have a high error rate in transcription. So much so that I am very nervous about doing that again. I have not decided what to do yet but am considering a mix of multiple online and offline wallets. I know this will increase the chances of errors and hacking but at least I wouldn't loose it all at once.