Suggestion for Andreas Schildbach's Bitcoin Wallet - page 2.

Forsyth Jones

hero member

Activity: 1120

Merit: 540

Duelbits - Play for Free | Win for Real

Thanks for replying dear user

When I type in software git bash: openssl enc -d -aes-256-cbc -a -in bitcoin-wallet-backup-2017-02-24 > bitcoin-wallet-decrypted-backup

It returns:

Quote

unknown option '-aes256-cbc'
options are
-in input file
-out output file
-pass pass phrase source
-e encrypt
-d decrypt
-a/-base64 base64 encode/decode, depending on encryption flag
-k passphrase is the next argument
-kfile passphrase is the first line of the file argument
-md the next argument is the md to use to create a key
from a passphrase. One of md2, md5, sha or sha1
-S salt in hex is the next argument
-K/-iv key/iv in hex is the next argument
-[pP] print the iv/key (then exit if -P)
-bufsize buffer size
-nopad disable standard block padding
-engine e use engine e, possibly a hardware device.
Cipher Types
-aes-128-cbc -aes-128-ccm -aes-128-cfb
-aes-128-cfb1 -aes-128-cfb8 -aes-128-ctr
-aes-128-ecb -aes-128-gcm -aes-128-ofb
-aes-128-xts -aes-192-cbc -aes-192-ccm
-aes-192-cfb -aes-192-cfb1 -aes-192-cfb8
-aes-192-ctr -aes-192-ecb -aes-192-gcm
-aes-192-ofb -aes-256-cbc -aes-256-ccm
-aes-256-cfb -aes-256-cfb1 -aes-256-cfb8
-aes-256-ctr -aes-256-ecb -aes-256-gcm
-aes-256-ofb -aes-256-xts -aes128
-aes192 -aes256 -bf
-bf-cbc -bf-cfb -bf-ecb
-bf-ofb -blowfish -camellia-128-cbc
-camellia-128-cfb -camellia-128-cfb1 -camellia-128-cfb8
-camellia-128-ecb -camellia-128-ofb -camellia-192-cbc
-camellia-192-cfb -camellia-192-cfb1 -camellia-192-cfb8
-camellia-192-ecb -camellia-192-ofb -camellia-256-cbc
-camellia-256-cfb -camellia-256-cfb1 -camellia-256-cfb8
-camellia-256-ecb -camellia-256-ofb -camellia128
-camellia192 -camellia256 -cast
-cast-cbc -cast5-cbc -cast5-cfb
-cast5-ecb -cast5-ofb -des
-des-cbc -des-cfb -des-cfb1
-des-cfb8 -des-ecb -des-ede
-des-ede-cbc -des-ede-cfb -des-ede-ofb
-des-ede3 -des-ede3-cbc -des-ede3-cfb
-des-ede3-cfb1 -des-ede3-cfb8 -des-ede3-ofb
-des-ofb -des3 -desx
-desx-cbc -id-aes128-CCM -id-aes128-GCM
-id-aes128-wrap -id-aes192-CCM -id-aes192-GCM
-id-aes192-wrap -id-aes256-CCM -id-aes256-GCM
-id-aes256-wrap -id-smime-alg-CMS3DESwrap -idea
-idea-cbc -idea-cfb -idea-ecb
-idea-ofb -rc2 -rc2-40-cbc
-rc2-64-cbc -rc2-cbc -rc2-cfb
-rc2-ecb -rc2-ofb -rc4
-rc4-40 -rc4-hmac-md5 -seed
-seed-cbc -seed-cfb -seed-ecb
-seed-ofb

Then I type the backup password: -k ******************

It returns something like an error. Surely I did it wrong? Please if you can explain the right command, because I did according:

Quote

DECRYPTING

You now have your backup file on your PC. Wallet backups are encrypted. Let's decrypt it using:

openssl enc -d -aes-256-cbc -a -in bitcoin-wallet-backup-testnet-2014-11-01 > bitcoin-wallet-decrypted-backup

It will ask you for a decryption password, which is your backup password. If it prints
"bad password" you've got the wrong password, but if it doesn't print anything your password might
still be wrong. We can only be sure by looking at the decrypted data.

HI-TEC99

legendary

Activity: 2772

Merit: 2846

I agree there should be an easy way to export private keys, but this was Andreas Schildbach's response to an earlier request for adding that option.

Quote from: ?? on ??

Private keys are not meant to be moved around, because they are very sensitive to theft. In fact the only reason to move them out of the app is a backup of the keys (which is unfortunately necessary).

If you want to move value to another wallet, use a standard Bitcoin transaction. That's much safer!

As the github readme instructions are complicated I posted simplified instructions for exporting private keys below.

First get your wallet file off your android phone. You might have to restart your phone it before you can see it.

Quote from: dooglus on August 28, 2015, 09:02:17 PM

Looking at the protobuf backup in a text editor, I see it starts like this:

Notice the 12 words in the middle there? That's the BIP32 mnenomic for the wallet - and that's all we need.

Copy the 12 words, paste them into https://dcpos.github.io/bip39/, go to the BIP32 tab, put "m/0'/0" into the "BIP32 Derivation Path" field, and there are all your receiving private keys. Then put "m/0'/1" in the same box and see all your change address private keys. You can toggle off the paths and addresses, generate as many as you need, then copy/paste them into a text file for importing into the CLAM wallet.

Here's a screenshot of the Android wallet, showing my receiving addresses:

and here's a screenshot of the dcpos bip39 page showing the same addresses along with the private keys:

Note that if you put "m/0'" into the "BIP32 Derivation Path" field, it shows you the same xpub string that the Android wallet app shows you when you go to "Settings>Diagnostics>Show xpub".

Rather than forcing people to jump through all the "simplified" hoops above it would be simpler just to include an option to export private keys from the wallet.

Forsyth Jones

hero member

Activity: 1120

Merit: 540

Duelbits - Play for Free | Win for Real

Well, I saw in this topic many requests for help on how to decode the backup that contains the private keys of this wallet mobile, since the wallet only allows you to send and receive, but you can not sign addresses Well there should be this option: Export private keys without Encrypt this export file. For if the private keys are mine, I have the right to export the privkeys of this wallet, for I am the sole owner of them.

I know you have a means of decoding the backup by following this manual: https://raw.githubusercontent.com/bitcoin-wallet/bitcoin-wallet/master/wallet/README.recover

But you have to understand that not everybody understands programming, and this manual is difficult to follow, would not it be easier to have an option in the app: "Export private keys"? We users know that handling the private keys is dangerous and so.

Is there no way I can backup if this backup is only for this wallet, and if I want to import the private keys into Bitcoin core or Electrum? To sign addresses for example ??

It seems that there was this option in older versions but why did they remove it?

I really like this wallet because it seems to be the simplest and most practical. But I only have this criticism. Please leave the option to export the private keys if we need to import into other alternative clients.

Thanks.

Topic: Suggestion for Andreas Schildbach's Bitcoin Wallet - page 2. (Read 2470 times)