Difference between revisions of "Securing your wallet"

From Bitcoin Wiki
Jump to: navigation, search
m (eWallet: Fix link again.)
Line 328: Line 328:
Storing bitcoins with an eWallet provider incurs risks as well. These are described further on the [[eWallet]] article.
Storing bitcoins with an [[eWallet]] provider incurs risks as well. Basically you grant the third party, in this case eWallet, full access to your wallet. These eWallets, or Electronic Wallets have a number of pros and cons. For example, you can access your wallet on any computer in the world, but the wallet can be forged or hacked and your bitcoins could be lost. You can also get eWallet applications for your Android phone, which also download the block chain like the normal client but allow the user to send bitcoins by QR code or NFC. The problem with this is that Bitcoins can be intercepted through means of mobile hacking.
==See Also==
==See Also==

Revision as of 07:22, 13 August 2011


Wallet security can be broken down into two independent goals:

  1. Protecting your wallet against loss.
  2. Protecting your wallet against theft.

In the case that your current wallet hasn't been protected adequately (e.g. put online with a weaker password):

  1. Making a new secure wallet, using appropriate long-term protection.

For a brief overview see also: Wallet Security Dos and Don'ts

Technical Background

Bitcoin transactions send Bitcoins to a specific public key. A Bitcoin address is an encoded hash of a public key. In order to use received Bitcoins, you need to have the private key matching the public key you received with. This is sort of like a super long password associated with an account (the account is the public key). Your Bitcoin wallet contains all of the private keys necessary for spending your received transactions. If you delete your wallet without a backup, then you no longer have the authorization information necessary to claim your coins, and the coins associated with those keys are lost forever.

The wallet contains a pool of queued keys. By default there are 100 keys in the key pool. The size of the pool is configurable using the "-keypool" command line argument. When you need an address for whatever reason (send, “new address”, generation, etc.), the key is not actually generated freshly, but taken from this pool. A brand new address is generated to fill the pool back to 100. So when a backup is first created, it has all of your old keys plus 100 unused keys. After sending a transaction, it has 99 unused keys. After a total of 100 new-key actions, you will start using keys that are not in your backup. Since the backup does not have the private keys necessary for authorizing spends of these coins, restoring from the old backup will cause you to lose Bitcoins.

Creating a new address generates a new pair of public and private keys, which are added to your wallet. Each keypair is mostly random numbers, so they cannot be known prior to generation. If you backup your wallet and then create more than 100 new addresses, the keypair associated with the newest addresses will not be in the old wallet because the new keypairs are only known after creating them. Any coins received at these addresses will be lost if you restore from the backup.

The situation is made somewhat more confusing because the receiving addresses shown in the UI are not the only keys in your wallet. Each Bitcoin generation is given a new public key, and, more importantly, each sent transaction also sends some number of Bitcoins back to yourself at a new key. When sending Bitcoins to anyone, you generate a new keypair for yourself and simultaneously send Bitcoins to your new public key and the actual recipient's public key. This is an anonymity feature – it makes tracking Bitcoin transactions much more difficult.

So if you create a backup, do more than 100 things that cause a new key to be used, and then restore from the backup, some Bitcoins will be lost. Bitcoin has not deleted any keys (keys are never deleted) – it has created a new key that is not in your old backup and then sent Bitcoins to it.

Making a new wallet

In the case that a wallet has been distributed, or stored, in a (real or potential) compromised state, it is wise to create a new wallet and transfer the full balance of Bitcoins to an address contained only in the newly created wallet.

For example, this will be necessary if one created a wallet with a password of 12 characters, as suggested. However a few years have passed and the wallet is now more easily compromised. Just re-encrypting isn't secure. One needs to make a new wallet and make the old wallet worthless (spending the funds to the new wallet).

Making a secure workspace


The first step is to make a new user, so run:

adduser new_user_name

as root. When you get to the prompt 'Enter the new value, or press ENTER for the default', just keep hitting ENTER.

Then switch user to the new user. To get to the new user you can use the switch user icon for your system, which on Ubuntu is in the 'System/Quit' screen, or if there is no switch icon on your system you can log out and log back in as the new user. Then click on a folder in the new user to display the file browser, then keep going up folders until you see the new user home directory, then right click to bring up the Properties dialog, then click on the Permissions tab, then in the Others section, set the folder access to None.

For secure browsing, open Firefox, and then go into the Edit menu and click Preferences. Starting from the left, click on the General tab, and in the 'Startup/When Firefox starts' pop up menu, choose 'Show a Blank Page'. Then click on the Content tab, and deselect 'Load images automatically' and deselect 'Enable Javascript'. Then click on the Privacy tab, and in the 'History/Firefox will' pop up menu, choose 'Never remember history'. Then click on the Security tab, and in the Passwords section, deselect 'Remember passwords for sites' and deselect 'Use a master password'. Then click on the Advanced tab, then click on the Update tab, and then in the 'Automatically check for updates to' section, deselect 'Add-ons' and 'Search Engines'.

When javascript is disabled, the linux download page will not download automatically, so you'll have to click on the 'direct link' part of the "Problems with the download? Please use this 'direct link' or try another mirror." line.

After you've made your secure new user, to maintain security you should use it only for bitcoin.

It's also a good idea to encrypt the Home directory of whatever user you run Bitcoin under using ecryptfs-utils. To do this:

  1. If the Home directory is not empty you should back it up first, by just copying the data to an external drive or something.
  2. install ecryptfs-utils (on Ubuntu: sudo apt-get install ecryptfs-utils)
  3. log out of X (graphical system) and press Ctrl+Alt+F1 to login to the command shell (you must be logged out or some files will be open and the tool won't be able to encrypt your data)
  4. change directory to something that's not in your home folder (ex: cd / )
  5. run the migration tool (on Ubuntu: sudo ecryptfs-migrate-home -u username)
  6. if it's successful, you can now press ALT+F8 to go back to the GUI and login
  7. run 'ecryptfs-unwrap-passphrase' and WRITE DOWN OR SAVE THE CODE IT RETURNS because you will need it if you ever have to pull your data off while the OS is not working. (You can run it again later if you need to, but run it now so that you can get your data if your Linux install gets botched.)
  8. run 'ecryptfs-setup-swap' to encrypt your swap partition (the encrypted folder data is not encrypted while it's in memory, and so if it's ever sent to the swap partition it can be stolen from there unless that too is encrypted - be aware that this will mean you cannot use Hibernate anymore, as the bootloader won't be able to restore the hibernation data)

(instructions from [1])


Backup all data (500MB)

Follow these instructions to backup all the bitcoin data (wallet and block chains) to an encrypted disk image.

  1. Open Disk Utility
  2. Click New Image and choose 500MB, 128-bit or 256-bit (faster or more secure) encryption and single partition.
  3. Save it somewhere you won't lose it (like your Wuala, Dropbox, Strongspace or whatever)
  4. Choose a safe and strong password
  5. Move everything from ~/Library/Application Support/Bitcoin/ to the image
  6. Symlink it back so the app would be able to use it
ln -s /Volumes/Bitcoin ~/Library/Application Support/Bitcoin

Don't forget to mount your image before using Bitcoin and unmount after quitting it.

Backup just wallet.dat (40MB)

Follow these instructions to backup just the wallet.dat file. This results in a smaller disk image, but it's more complicated to do.

  1. Open Disk Utility
  2. Click New Image and choose 40MB, 128-bit or 256-bit (faster or more secure) encryption and single partition.
  3. Save it somewhere you won't lose it (like your Wuala, Dropbox, Strongspace or whatever)
  4. Choose a safe and strong password
  5. Move your wallet.dat file to the image
  6. Symlink it back so the app would be able to use it
ln -s /Volumes/Bitcoin/wallet.dat ~/Library/Application Support/Bitcoin/wallet.dat
Mount Wallet and launch Bitcoin

Don't forget to mount your image before using Bitcoin and unmount after quitting it.

Note: If you start the Bitcoin application without having the image mounted, the application will overwrite your symlink with a new wallet. If that happens, don't panic. Just delete the new wallet.dat, mount the image, and recreate the symlink like above.

Automation: You can create a small application using Automator (included in OS X) to automatically mount the wallet and then launch Bitcoin App. See the Screenshot on how to do this.

If one doesn't want to use encrypted Disk images, then a small shell script can be used instead that takes care of decrypting the wallet, launching bitcoin client, and encrypting it after the client exits. This script works on both OSX and Linux: bitcoin-launch-script


If you are using Windows XP or Windows 7, you can keep your wallet on an encrypted disk image created by third-party software, such as TrueCrypt (open source) or Jetico BestCrypt (commercial). You can probably do the same with Windows Vista or Windows 2000.

NOTE: You should configure BitCoin in this manner only on computers where you use BitCoin, but do not use that computer to mine. For example, this is a good configuration for a notebook or tablet computer.

Assuming that you have installed the Windows BitCoin client and run it at least once, the process is described below.

To mount the BitCoin data directory on an encrypted drive

  1. Use the third-party disk image encryption program of your choice to create and mount an encrypted disk image of at least 100 MB in size.
  2. Locate the BitCoin data directory, and copy the directory with all contents to the encrypted drive.

    For help finding this directory, see Locating BitCoin's Data Directory.

  3. Create a Windows shortcut that starts BitCoin with the -datadir parameter and specifies the encrypted drive and directory.

    For example, if you installed Bitcoin in the default directory, mounted your BitCoin encrypted drive as E:\, and stored your BitCoin data directory on it as Bitcoin, you would type the following command as the shortcut Target:

    C:\Program Files\Bitcoin\bitcoin.exe -datadir=E:\Bitcoin
  4. Open BitCoin's settings and configure it NOT to start automatically when you start Windows.

    This is to allow you to mount the BitCoin encrypted disk image before starting BitCoin.

  5. Shut down BitCoin, and then restart it from the new shortcut.

After doing this, any time you want to use BitCoin, you must first mount the BitCoin encrypted disk image using the same drive designation, and then run BitCoin from the shortcut that you created, so that it can find its data and your wallet. :-)

Locating BitCoin's data directory

The data directory is the location where Bitcoin's data files are stored, including the wallet data file.


Go to Start -> Run (or press WinKey+R) and run this:

explorer %APPDATA%\BitCoin

BitCoin's data folder will open. For most users, this is the following locations:

C:\Documents and Settings\YourUserName\Application data\BitCoin (XP)

C:\Users\YourUserName\Appdata\Roaming\BitCoin (Vista and 7)

"AppData" and "Application data" are hidden by default.


By default BitCoin will put its data here:


You need to do a "ls -a" to see directories that start with a dot.

If that's not it, you can do a search like this:

find / -name wallet.dat -print 2>/dev/null


By default BitCoin will put its data here:

~/Library/Application Support/Bitcoin/


Note: I would strongly recommend against using Dropbox to back up your Bitcoin data due to security concerns such as:

  1. the fact that they store your encryption key (meaning that a disgruntled Dropbox employee or an attacker who gained access to the system could decrypt your Dropbox data and steal your Bitcoins)
  2. the fact that the Dropbox client only needs a password for the first login. After it authenticates once, the server assigns it a token which it uses to show that, at one time, its user knew the password rather than sending the actual password (meaning that if you ever use the Dropbox client on another PC, that PC's users can access your Dropbox - even if you change your password - and can steal your Bitcoins or get a virus that will steal your Bitcoins).

For these reasons, I personally prefer to use Wuala, which does not store your encryption key and requires a password each time (the client can be set to remember your password, but the server will check each time to make sure that the client is sending the correct password). Like Dropbox, the basic, lowest-storage-space account with Wuala is free of charge, and coincidentally, Wuala is experimenting with allowing users to pay for "upgraded" plans using Bitcoin.

In fact, whether you use Dropbox as your backup or not, use what Steve Gibson calls "pre-Internet encryption" (which he actually discussed in the context of Dropbox's security concerns) and use some form of encryption on the files before you back them up, just in case someone other than yourself ever gains access to that backup. Make sure to pick a password that's memorable but secure.

The only file you need to back up is "wallet.dat". Ensure that BitCoin is closed, copy this file somewhere else, encrypt it, and put it somewhere safe. Ideally, you would put this file in two places: one nearby, and one 100+ miles away.

You can use the backupwallet JSON-RPC command to back up without shutting down Bitcoin.

General Solutions

Your wallet.dat file is not encrypted by BitCoin. Anyone who can access it can easily steal all of your coins. Use one of these encryption programs if there is any chance someone might stumble upon your wallet.

  • 7-zip - Supports strongly-encrypted archives.
  • AxCrypt
  • lrzip - Compression software for Linux and OSX that supports very high grade password protected encryption
  • TrueCrypt - Volume-based on-the-fly encryption (for advanced users)
  • WinRar - Commonly used archive software that supports verification records and encryption.

There is also a list of open source encryption software.

Decrypting and encrypting the wallet.dat every time you start or quit the Bitcoin client can be tedious (and outright error-prone). If you want to keep your wallet encrypted (except while you're actually running the Bitcoin client), it's better to relegate the automation to a small shell script that handles the en/decryption and starting up Bitcoin client for you (Linux and OSX).

There is also a method to Print out and encrypt your Wallet.dat as a special barcode. See details here: WalletPaperbackup

Password Strength

Brute-force password cracking has come a long way. A password of random [a-Z] [0-9] [!-~] of 8 characters long was previously thought secure but can be trivially solved now (using appropriate hardware). The recommended length is at least 12 characters long. You can also use a multi-word password. The Usability of Passwords

However, simply using dictionary words is also insecure as it opens you up to a dictionary attack. If you use dictionary words, be sure to throw random symbols and numbers in the mix as well.

A good way to create secure but easy-to-remember passwords is to pick a password (ex: d0g) and pad it with a good number of repeated characters afterward (such as 10 $ signs - so d0g becomes d0g$$$$$$$$$$) - this is just as cryptographically secure as a random password of equal length so long as the attacker does not know which symbol you are following your "word" with and how many times it is repeated. (source)

If you use keyfiles in addition to a password, it is unlikely that your encrypted file can ever be cracked using brute force methods, even 10 years from now when even a 12 character password might be too short.

Assume that any encrypted files you store online (eg. gmail, Dropbox) will be stored somewhere forever and can never be erased.

Choosing Your Password

Make sure you pick at least one character in each group:

 Lowercase: abcdefghijklmnopqrstuvwxyz
 Number: 1234567890
 Symbol: `~!@#$%^&*()-_=+\|[{]};:'",<.>/? (space)
 09 char = insecure
 10 char = low security
 11 char = medium security
 12 char = good security (good enough for your wallet)
 13 char = v.good enough for anything.

Storage of Archive

One of the most simple methods for storing a appropriately encrypted archive of your wallet.dat file is to send the archive as an email attachment to your own e-mail address. Services like gmail.com use very comprehensive distributed networks that make the loss of data very unlikely. One can even obfuscate the name of the files within the archive, and name the archive something less inviting, such as: 'personal notes' or 'car insurance'.

Another solution is to use a file storage service like Wuala ( encrypted, instructions), Dropbox and others, including the more secure SpiderOak.

Linux solution

Linux users can setup backups using cron by telling it to run a backup script at set intervals of time. Run 'crontab -e' and add this line near the bottom:

01 */1 * * * /usr/local/bin/backupwallet.sh

This cron line will run the /usr/local/bin/backupwallet.sh script at the 01 minute of every hour. Remember to add a newline after the last line of the crontab file, or else the last line won't run. You may also wish to ignore the script's output by appending " > /dev/null 2>&1" to the line (this will also prevent emails from being sent).

Create /usr/local/bin/backupwallet.sh:

# /usr/local/bin/backupwallet.sh
# Performs backup of bitcoin wallet.
# Written by: https://en.bitcoin.it/wiki/Securing_your_wallet

# Standard Options
TS=$(date "+%Y%m%d-%H%M")
BITCOIN=bitcoind  # /path/to/bitcoind
GPG=gpg  # /path/to/gpg
GPG_USER=username  # Username of gpg recipient. User should have gpg setup.
USE_SHRED=0  # Flip to 1 to use `shred` instead of `rm`.
SHRED_OPTS='--force --iterations=9 --zero --remove'

# Storage Options
# Only 1 set of options should be un-commented (the last one will be used).
# Update CP_DEST paths as neccessary.
# CP - Storage on a local machine. Could be Dropbox/Wuala folder.
#CP_DEST='/var/data/backups/'  # '~/Dropbox/', etc.
# SSH - Storage on a remote machine.
# S3 - Storage on Amazon's S3. Be sure s3cmd is installed and properly setup.
# You may need "s3cmd put --force" if you use a sub-directory in CP_DEST.
#CP=s3cmd put

do_clean() {
  # Remove temporary wallets.
  if [ 1 -eq $USE_SHRED ]; then

do_fail() {
  echo failed!
  exit 1

# Perform the backup.
echo -n Making backup...
$BITCOIN backupwallet $WALLET
[ ! -s "$WALLET" ] && do_fail  # If the backup does not exist or is empty, fail.
echo done.
echo -n Encrypting backup...
$GPG -r $GPG_USER --output $WALLET_E --encrypt $WALLET
[ 0 -ne $? ] && do_fail  # If gpg returns a non-zero result, fail.
echo done.
echo -n Copying to backup location...
[ 0 -ne $? ] && do_fail  # If the $CP command returns a non-zero result, fail.
echo done.

exit 0

The shell script:

  • Calls bitcoind backupwallet to create a time/date-stamped wallet.
  • GPG encrypts the wallet with your public key.
  • Copies the result using one of several storage options (cp, scp, and s3cmd).
  • Uses the rm or shred command to remove the temporary wallet files.

Be sure to modify the script options to fit your setup. After you save, make sure the file can be executed properly by the cron user. Common permissions for files in /usr/local/bin/ can be applied using (verify with your distribution!):

cd /usr/local/bin/ && chown root:root backupwallet.sh && chmod 755 backupwallet.sh


Assuming your backup is recent enough that you haven't used up all of your key pool... restoring a wallet to a new (or old) location and rescanning the block chain should leave you with all your coins. Just follow these steps:

  • Quit bitcoin(d).
  • Copy your backed up wallet.dat into your bitcoin profile directory.
  • If copying into existing profile, delete file blkindex.dat and blk0001.dat to make the client re-scan the block chain.

And you'll be good as new.

Erasing Plain Text Wallets

A good practice is to keep at least two wallets, one as a "current account" for everyday transactions and one as a "savings account" where you store the majority of your Bitcoins.

The "savings account" wallet should be backed up in encrypted form only and all plaintext copies of this wallet should be erased. In case someone gains unauthorised access to your computer (either by physically stealing it or by exploiting a system vulnerability via the internet), they will only be able to spend the coins in your "current account" wallet.

In most operating systems, including Windows, Linux, and Mac OS X, simply deleting a wallet.dat file will not generally destroy it. It is likely that advanced tools can still be used to recover the wallet.dat file, even after it has been deleted.

The Linux shred command can be used to overwrite the wallet file with random data prior to deleting; this particular copy of the file will then be practically impossible to recover. Using shred (and similar tools on Windows) however does not guarantee that still other copies don't exist somewhere hidden on your HD. That will depend on your system configuration and what packages you have installed. Some system restore and backup tools, for instance, create periodic snapshots of your filesystem, duplicating your wallet.dat.

In Mac OS, the equivalent of shred is srm (introduced in Leopard). Using the Finder to remove files, clicking "Secure Empty Trash" in the Finder menu will shred the contents of the trash can. As with any OS this doesn't guarantee that there are not other copies elsewhere on your system.

For Windows, the built-in command cipher /W will shred all previously-deleted files. CyberShredder can securely deleted individual files.


Storing bitcoins with an eWallet provider incurs risks as well. Basically you grant the third party, in this case eWallet, full access to your wallet. These eWallets, or Electronic Wallets have a number of pros and cons. For example, you can access your wallet on any computer in the world, but the wallet can be forged or hacked and your bitcoins could be lost. You can also get eWallet applications for your Android phone, which also download the block chain like the normal client but allow the user to send bitcoins by QR code or NFC. The problem with this is that Bitcoins can be intercepted through means of mobile hacking.

See Also