Pywallet 2.2: manage your wallet [Update required]

[PrintCoins]

I don't have my wallet encrypted, and tried to use pywallet on 0.4, and it threw an error because of the version number.

I went into the code, and changed maxversion from 32400 to 52400 and then imported into my wallet. Seemed to work fine.

(Warning, may kill your wallet)

[finway]

Must try this someday.

[cjp]

I tried it with Bitcoin 0.4 (not encrypted), and it worked fine for me (I only tried dumping the wallet contents and importing a private key).

Having said that, I'll still backup my wallet each time before using Pywallet.

[Transisto]

This is what I get, :

Code:

 C:\Users\M7\AppData\Roaming\Bitcoin>pywallet.py --web --port 8989
  File "C:\Users\M7\AppData\Roaming\Bitcoin\pywallet.py", line 109
    _p = 0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFEFFFFFC2FL
                                                                           ^
SyntaxError: invalid syntax

[btc_artist]

Thanks for this jackjack!

[jackjack]

This is what I get, :

Code:

 C:\Users\M7\AppData\Roaming\Bitcoin>pywallet.py --web --port 8989
  File "C:\Users\M7\AppData\Roaming\Bitcoin\pywallet.py", line 109
    _p = 0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFEFFFFFC2FL
                                                                           ^
SyntaxError: invalid syntax

I think you used Python 3, you should try with Python 2

[BkkCoins]

I saw suggested on the forum that pywallet may work to import an address if used with the bitcoind client and the wallet is unlocked first. This seems like an easy way to work around encryption issues but I'm wondering if anyone has actually tried this?

Even though the wallet is unlocked briefly (by invoking command line to daemon client) that doesn't imply to me that the wallet file is actually then updatable by pywallet as it's possible/likely that an unlocked wallet is simply held in memory (at least I wouldn't assume that the disk file is re-written unencrypted). Anyone know for sure?

(btw I'm using the new 0.5.0 bitcoind as well as bitcoin-qt, which apparently writes the wallet differently than 0.4.0)

[splatster]

When trying to install ecdsa on OS X, I get:

Code:

Searching for ecdsa
Reading http://pypi.python.org/simple/ecdsa/
Download error: [Errno 65] No route to host -- Some packages may not be found!
Couldn't find index page for 'ecdsa' (maybe misspelled?)

Any alternative ways to install?

EDIT: Never mind, the site was down or something, but it's back up now.

EDIT #2: I ran into the version mismatch problem, so I edited the source and made max version 51000.  Works perfectly with 0.5.1 as far as I can see.

[K1773R]

Hi there!
I had to leave for some time, sorry for that
I won't have as much time as before but I won't leave for months anymore

The priority is of course to make pywallet able to deal with encrypted wallets
I can't give you any ETA but I'll do my best

Btw, thanks for your pull requests on Github, I'll check and commit them

any progress? do you need help?

[slush]

I'm trying wallet recovery on corrupted notebook disk, but it failed on IOError when pywallet touched corrupted sector. Following code fixes this issue by skipping bad block in first_read():

Code:

                try:
                        data = os.read (fd, inc)
                except Exception as exc:
                        os.lseek(fd, inc, os.SEEK_CUR)
                        print str(exc)
                        i += inc
                        continue

[jackjack]

Hi there!
I had to leave for some time, sorry for that
I won't have as much time as before but I won't leave for months anymore

The priority is of course to make pywallet able to deal with encrypted wallets
I can't give you any ETA but I'll do my best

Btw, thanks for your pull requests on Github, I'll check and commit them

any progress? do you need help?

Tbh I didn't even start
I really need time so yes I need help

If someone have some free time and want to help me, please let me know, especially if you are a programmer

[jackjack]

I'm trying wallet recovery on corrupted notebook disk, but it failed on IOError when pywallet touched corrupted sector. Following code fixes this issue by skipping bad block in first_read():

Code:

                try:
                        data = os.read (fd, inc)
                except Exception as exc:
                        os.lseek(fd, inc, os.SEEK_CUR)
                        print str(exc)
                        i += inc
                        continue

Thanks, this will be added very soon

[K1773R]

Hi there!
I had to leave for some time, sorry for that
I won't have as much time as before but I won't leave for months anymore

The priority is of course to make pywallet able to deal with encrypted wallets
I can't give you any ETA but I'll do my best

Btw, thanks for your pull requests on Github, I'll check and commit them

any progress? do you need help?

Tbh I didn't even start
I really need time so yes I need help

If someone have some free time and want to help me, please let me know, especially if you are a programmer

atm i havent enough time, gonna send u a message when il have enough time until then i work a bit on my own changing ur code if this is ok

greetings

[slush]

My today's success story: Computer of friend of mine crashed two days ago. He went to some IT guy, asking for repair. That guy recommended "format & reinstall" (wow, are all issues with Windows still solving this way?) and asked, if backup of office document and some other stuff is enough for him. Today, friend called me that he has reformatted harddisk and fresh install of Windows and he completely forgot to his bitcoin wallet with 80 BTC, asking me if there is any way how to recover them. I played with pywallet some time ago and I barely noticed such cool feature of finding private keys on raw device, so I told him I'll try the recovery.

It went smooth (except that issue with corrupted blocks - which btw means that "format & reinstall" didn't fix previous issues with Windows) and his wallet has been fully recovered. Thank you jackjack for so cool application, small donation is going your way.

[0ni0ns]

I keep getting errors for anything I try to do from the web interface, but dumping the wallet and importing keys from the command line work fine. Is this an issue with 5xxxx wallet versions?

[jackjack]

My today's success story: Computer of friend of mine crashed two days ago. He went to some IT guy, asking for repair. That guy recommended "format & reinstall" (wow, are all issues with Windows still solving this way?) and asked, if backup of office document and some other stuff is enough for him. Today, friend called me that he has reformatted harddisk and fresh install of Windows and he completely forgot to his bitcoin wallet with 80 BTC, asking me if there is any way how to recover them. I played with pywallet some time ago and I barely noticed such cool feature of finding private keys on raw device, so I told him I'll try the recovery.

It went smooth (except that issue with corrupted blocks - which btw means that "format & reinstall" didn't fix previous issues with Windows) and his wallet has been fully recovered. Thank you jackjack for so cool application, small donation is going your way.

I'm glad it worked even after a reinstall! Thanks for the donation

I keep getting errors for anything I try to do from the web interface, but dumping the wallet and importing keys from the command line work fine. Is this an issue with 5xxxx wallet versions?

What's written in the console?

atm i havent enough time, gonna send u a message when il have enough time until then i work a bit on my own changing ur code if this is ok

greetings

Thanks


Also I just add the --dont_check_walletversion option to use 0.3.25+ wallet versions

[jackjack]

Is there any documentation about key encryption? Or anybody knowing how to encrypt/decrypt privkeys?
I can continue my research but if somebody already knows that it would be better

I have the passphrase and these data about the master key, how can I decrypt encrypted privkeys?

Code:

        "encrypted_key": "bda3f31ce15e5e2072fb4fbe7b6e6a55c2da23b067c4f5599a50fa053e617f72aecb31d73dea36bed72b57d19736ea93", 
        "nDerivationIterations": 62351, 
        "nDerivationMethod": 0, 
        "nID": 1, 
        "otherParams": "", 
        "salt": "f325081b21a3b80e"

[Gavin Andresen]

RE: documentation about key encryption:

See the comment at the top of crypter.h:

Code:

Private key encryption is done based on a CMasterKey,                                                                                                   
which holds a salt and random encryption key.                                                                                                           
                                                                                                                                                        
CMasterKeys are encrypted using AES-256-CBC using a key                                                                                                 
derived using derivation method nDerivationMethod                                                                                                       
(0 == EVP_sha512()) and derivation iterations nDeriveIterations.                                                                                        
vchOtherDerivationParameters is provided for alternative algorithms                                                                                     
which may require more parameters (such as scrypt).                                                                                                     
                                                                                                                                                        
Wallet Private Keys are then encrypted using AES-256-CBC                                                                                                
with the double-sha256 of the public key as the IV, and the                                                                                             
master key's key as the encryption key (see keystore.[ch]).                                                                                             

The way I think of it:  Take the passphrase and salt and SHA512-hash them nDerivationIterations times.  That gets you an encryption key and initialization vector.

Use those to AES-256-decrypt the encrypted_key master key.

Now you can AES-256-decrypt the private keys, using the master key as the key and the (double-sha256-hash) PUBLIC part of the keypair as the initialization vector.

The "SHA-512-hash them a bunch of times" is actually done by the OpenSSL EVP_BytesToKey routine-- documentation for that is here: http://www.openssl.org/docs/crypto/EVP_BytesToKey.html

[Red Emerald]

RE: documentation about key encryption:

See the comment at the top of crypter.h:

Code:

Private key encryption is done based on a CMasterKey,                                                                                                   
which holds a salt and random encryption key.                                                                                                           
                                                                                                                                                        
CMasterKeys are encrypted using AES-256-CBC using a key                                                                                                 
derived using derivation method nDerivationMethod                                                                                                       
(0 == EVP_sha512()) and derivation iterations nDeriveIterations.                                                                                        
vchOtherDerivationParameters is provided for alternative algorithms                                                                                     
which may require more parameters (such as scrypt).                                                                                                     
                                                                                                                                                        
Wallet Private Keys are then encrypted using AES-256-CBC                                                                                                
with the double-sha256 of the public key as the IV, and the                                                                                             
master key's key as the encryption key (see keystore.[ch]).                                                                                             

The way I think of it:  Take the passphrase and salt and SHA512-hash them nDerivationIterations times.  That gets you an encryption key and initialization vector.

Use those to AES-256-decrypt the encrypted_key master key.

Now you can AES-256-decrypt the private keys, using the master key as the key and the (double-sha256-hash) PUBLIC part of the keypair as the initialization vector.

The "SHA-512-hash them a bunch of times" is actually done by the OpenSSL EVP_BytesToKey routine-- documentation for that is here: http://www.openssl.org/docs/crypto/EVP_BytesToKey.html

I'd been wondering about this for awhile. Thanks for the info.

Glad to see you are working on this again jackjack.  Once I can retire one of my old wallets, I'll send you a donation.

[jackjack]

Thanks a lot Gavin, this will be very helpful!