Topic: Securing my wallet on Ubuntu: is my theory solid? (Read 1289 times)

Hello,

Thanks for the feedback.

I deliberately left out the backups part, to focus on the wallet-switching. I do backup, using the really handy DejaDup application. It stores encrypted versions on both amazon s3 and on a usb drive. Once each month I additionally run a small script that creates (unencrypted!) backups of some important files (my financial administration and such) and keys on a DVD, wich is stored in a secure place.

That thumbdrive solution looks a lot simpler then my move-around-wallet.dat solution. Will certainly look into that. Thanks!

use truecrypt and do BACKUP.

the fire burning your computer can steal your bitcoins, remember !
(dropbox works, don't forget to encrypt tho -.-)

I agree with jjhall.

If you use PIE (Pre Internet Encryption) before you store something online, then you are safe (as long as you use a strong password or you do not lose control of your private key if you use asymmetric* encryption).

If you PIE, they you can store your data safely online. You will just have to remember where you put them.

I take PIE a step further and encrypt data when it leaves my system (e.g., coping to a USB).  This way I can safely delete that file without having to shred. For this to work, I will not decrypt the file on the USB. 

* Also called public-key cryptography (which is what BitCoin uses by the way  ). See http://en.wikipedia.org/wiki/Public-key_cryptography for details.

Hence the reason I said to put a TrueCrypt container there, even if someone gets it it won't be useful as long as secure passwords are used.  Nothing is 100% secure of course, but that should be sufficient for most all cases.  If you're really paranoid, use GPG to encrypt the truecrypt volume before uploading it, of course you still have to keep safe backup copies of said GPG key.

Oooh.  Good read.  Thanks for the suggestions, guys

Hmmmm, I wouldn't trust dropbox right now:  they had a seucirty breach (due to a bug in an update) on Sunday that allowed full access to every account.  The only way, in my opinion, to have peace of mind, is to handle all security measures yourself.

Also you don't need to open your savings wallet when you transfer BTC into it.  Just send the coins to one of the addresses you've generated for it.  Since the transaction is pushed into the block chain it is done, regardless of whether the client is active or not.  You could send hundreds of coins to your savings wallet and not check it for months.  Once you do open it, it will download the block chain, and all of the transactions will show up.

As others have said, make sure you have multiple copies of your saving wallet on several forms of media, and in several physically separated locations.  Maybe even put a TrueCrypt container file containing your savings.wallet.dat on Dropbox or some similar service.

I would recommend using a thumb drive bootable edition of ubuntu for your savings account. That way every time you access your savings wallet, you are on a fresh copy of ubuntu and any trojans you may have gotten with your main OS will not effect your savings wallet. I put a guide together for all of you who are reading this and don't know what I'm talking about.

http://startbitcoin.com/how-to-create-a-secure-bitcoin-wallet/

Hello,

My conceptual setup is:

* A USB stick-drive, which is encryped and kept in a physical safe place, contains my savings wallet (savings.wallet.dat). I have always used this for a monthly backup of my private SSH and GPG keys.

* My local, SSD drive on my laptop has a wallet.dat containing some spending money and accepting donations/payments. I try to keep it under BTC5,-. The SSD drive is encrypted too, using Ubuntu's disk encryption option at installation (encryptfs aes). To avoid people peekin in when laptop is stolen or lost.

When I need to send money from my savings to my spending wallet, I
* Stop bitcoind
* Move wallet.dat tp spending.wallet.dat (rename)
* Mount the USB stick, read-writable
* Symlink: ln -s /media/secured_usb/savings.wallet.dat ~/.bitcoin/wallet.dat
* Restart bitcoind
* Send money to an address on my spending wallet
* Stop bitcoind
* Remove the symlink
* Move back the spending.wallet.dat to wallet.dat (rename)
* Start bitcoind

When I need to wire money from my spending onto my savings, I
* Send money to an address on my savings wallet
* Stop bitcoind
* Move wallet.dat into spending.wallet.dat
* Mount the USB stick, read-writable
* Symlink: ln -s /media/secured_usb/savings.wallet.dat ~/.bitcoin/wallet.dat
* Restart bitcoind
* Wait untill the transaction is confirmed.
* Stop bitcoind
* Remove the symlink
* Move back the spending.wallet.dat to wallet.dat (rename)
* Start bitcoind

I can see a few flawes: I my system itself is compromised by some trojan, it can still hijack my savings wallet when it is mounted, eventhough the window is small.
Also, there are many more files in .bitcoin which seem to contain metadata such as the addresses in use. Will this break when they suddenly see a completely different wallet.dat?

Am I missing some very important piece of the puzzle alltogether?

Regards,
  Bèr