Easy backup method?

[MacFall]

What if I were to email my wallet to myself with PGP encryption? That way it exists on my email server in case all my hardware goes boink. But would it be secure enough with PGP?

[1713920474]

1713920474

[1713920474]

1713920474

[1713920474]

1713920474

[1713920474]

1713920474

[1713920474]

1713920474

[1713920474]

1713920474

[koin]

What if I were to email my wallet to myself with PGP encryption? That way it exists on my email server in case all my hardware goes boink. But would it be secure enough with PGP?

i hate seeing email used as a backup / file archive but i suppose the wallet.dat is such a small file that sending it encrypted through email is not going to consume too much space.

pgp itself is secure.  if you have your email client do stuff like "remember password" or something like that, then you might not have a secure wallet.

and don't forget the rule of thumb.   you don't have a backup until you've verified with testing that your backup can be restored.

[epi 1:10,000]

you could setup a Trucrypt encrypted file container and store your wallet in that on Wuala/Dropbox.

[bitjet]

You could use 7zip and put the file in a self extracting archive with 256bit encryption. Quick and easy. Rename the file, send it to your gmail let it hangout.

[LegitBit]

Dropbox or a Flash drive encrypted with 7-Zip is how I'd go about it.

A TrueCrypt virtual volume is a bit of a pain if you are planning on updating this backup regularly. Go the path of lease resistance and high security, too complicated and you may end up not backing up for months.. in which case your backup will be useless.

On the other hand, a TrueCrypt physical disk in mirrored raid would be best.

[BitCointransfers]

be very careful man,, buddy on here just reported losing 7208 fucking coins!

[mrkva]

I made a simple backup script with des3 encryption (openssl) and option for remote backup (scp).
You can as well send yourself as encrypted file via e-mail (it's in a tar - so very small).

https://github.com/mrkva/BitcoinBackup.sh

[unk]

for backups that are being distributed en masse and stored long-term, you'd be well advised to use a modern cypher rather than 3des or cast-128. truecrypt gives you good options. at least pick aes256 manually if you're using gpg.

[mrkva]

for backups that are being distributed en masse and stored long-term, you'd be well advised to use a modern cypher rather than 3des or cast-128. truecrypt gives you good options. at least pick aes256 manually if you're using gpg.

I see my solution very useful in case of dead harddrive, and when backed up on e-mail/server, you can access your wallet without your key file, so anywhere as far as you remember your password.

[unk]

i wasn't suggesting public-key cryptography; gpg also handles symmetric cyphers. it may not make much difference in practice depending on your threat model, but 3des is strictly a poorer choice than aes256.

[mrkva]

i wasn't suggesting public-key cryptography; gpg also handles symmetric cyphers. it may not make much difference in practice depending on your threat model, but 3des is strictly a poorer choice than aes256.

Thanks, I fixed it. It is now using AES256. ( https://github.com/mrkva/BitcoinBackup.sh )
Maybe you know some way how to promote it?