You can import your encrypted blockchain.info wallet backups into MultiBit.
There is a detailed how to here:
https://multibit.org/en/help/v0.5/help_movingAWallet.html
Topic: How do I decrypt the Blockchain.info email backup wallet? (Read 9639 times)
Does this apply to paper wallets as well as encrypted digital backups of them? So that if blockchain disappeared getting Bitcoins back would be tough.
See http://bitcoin.stackexchange.com/a/3037/659 (expand all the comments) and in particular https://gist.github.com/2757171 for the newest version of the Python code to decrypt the wallet.
Why the heck wasn't plain old AES good enough? And while you could technically do that with "standard UNIX tools", it's a heck of a task.
Thanks for the info, though, this should let me figure it out.
Edit:
Got an email from the blockchain.info tech support guy, he confirmed that the wallets can no longer be decrypted easily with "standard" tools.
That's bullshit. So much for his paper wallet cold storage solution.
Yeah, I agree. I mean, there are security considerations, but I'm sure one could base them off of some easily repeatable task instead of a complex-as-shit byte swapping and hashing algorithm.
See http://bitcoin.stackexchange.com/a/3037/659 (expand all the comments) and in particular https://gist.github.com/2757171 for the newest version of the Python code to decrypt the wallet.
Why the heck wasn't plain old AES good enough? And while you could technically do that with "standard UNIX tools", it's a heck of a task.
Thanks for the info, though, this should let me figure it out.
Edit:
Got an email from the blockchain.info tech support guy, he confirmed that the wallets can no longer be decrypted easily with "standard" tools.
That's bullshit. So much for his paper wallet cold storage solution.
See http://bitcoin.stackexchange.com/a/3037/659 (expand all the comments) and in particular https://gist.github.com/2757171 for the newest version of the Python code to decrypt the wallet.
Why the heck wasn't plain old AES good enough? And while you could technically do that with "standard UNIX tools", it's a heck of a task.
Thanks for the info, though, this should let me figure it out.
Edit:
Got an email from the blockchain.info tech support guy, he confirmed that the wallets can no longer be decrypted easily with "standard" tools.
Any idea which part of the multibit source handles this? I am having trouble finding it.
It is in here:
https://github.com/jim618/multibit/blob/v0.4/src/main/java/com/piuk/blockchain/MyWallet.java
See http://bitcoin.stackexchange.com/a/3037/659 (expand all the comments) and in particular https://gist.github.com/2757171 for the newest version of the Python code to decrypt the wallet.
Any idea which part of the multibit source handles this? I am having trouble finding it.
You can import the blockchain.info encrypted backups into MultiBit (including the double encrypted ones).
Piuk wrote an importer routine and it is part if the 'Tools | Import Private Keys' functionality.
There is a how to here:
http://multibit.org/help_importingPrivateKeys.html
Piuk wrote an importer routine and it is part if the 'Tools | Import Private Keys' functionality.
There is a how to here:
http://multibit.org/help_importingPrivateKeys.html
Even if their API works, I am more concerned with the possibility that they somehow go out of business. I would like to have a surefire way to recover my backup, if needed.
I hear ya! maybe the password is screwing it up? Do you have funny characters or something? That was my issue with the API. I needed to url encode my password
Even if their API works, I am more concerned with the possibility that they somehow go out of business. I would like to have a surefire way to recover my backup, if needed.
Double encryption might be the issue but i can't say for sure.
So..... care to tell me how you got the api working! :-D
So..... care to tell me how you got the api working! :-D
Even though retrieving the address for my wallet worked fine through the Blockchain API (unlike what happened to unclemantis, on his other thread), I can't seem to be able to decrypt a backup of the same wallet on my computer with openssl either. I have double-encryption enabled, may that be the problem?
Blockchain.info regularly sends me an encrypted backup of the wallet I have stored with them. According to the email, I can either use their online services or "standard Unix tools" to decrypt this backup. Now, I assume they mean using the openssl command line tool or something, but I am having trouble figuring it out. I have tried the following:
and since it looks like it might be base64 encoded, I also tried
However, the first one gives a "Bad magic number" error and the second one gives an "error reading from file" (so I was probably wrong about base64). I also tried both of these with aes-256-ebc.
Code:
openssl enc -d -in /Users/User/Downloads/wallet.aes.json -out /tmp/wallet -aes-256-cbc
and since it looks like it might be base64 encoded, I also tried
Code:
openssl enc -d -in /Users/User/Downloads/wallet.aes.json -out /tmp/wallet -aes-256-cbc -base64
However, the first one gives a "Bad magic number" error and the second one gives an "error reading from file" (so I was probably wrong about base64). I also tried both of these with aes-256-ebc.
I maybe be having the same issue. Decrypting is not working for me at all. Also their API is not decrypting their wallet right.
Blockchain.info regularly sends me an encrypted backup of the wallet I have stored with them. According to the email, I can either use their online services or "standard Unix tools" to decrypt this backup. Now, I assume they mean using the openssl command line tool or something, but I am having trouble figuring it out. I have tried the following:
and since it looks like it might be base64 encoded, I also tried
However, the first one gives a "Bad magic number" error and the second one gives an "error reading from file" (so I was probably wrong about base64). I also tried both of these with aes-256-ebc.
Code:
openssl enc -d -in /Users/User/Downloads/wallet.aes.json -out /tmp/wallet -aes-256-cbc
and since it looks like it might be base64 encoded, I also tried
Code:
openssl enc -d -in /Users/User/Downloads/wallet.aes.json -out /tmp/wallet -aes-256-cbc -base64
However, the first one gives a "Bad magic number" error and the second one gives an "error reading from file" (so I was probably wrong about base64). I also tried both of these with aes-256-ebc.
Jump to: