Bitcoin Forum

Bitcoin => Bitcoin Technical Support => Topic started by: IlbiStarz on June 20, 2011, 12:49:45 AM



Title: Am I Encrypting Right?
Post by: IlbiStarz on June 20, 2011, 12:49:45 AM
So...am I doing this right? What I did:

1. Turn off Bitcoin.

2. Copy the wallet.dat file.

3. I used Winrar to make an encryption.

4. Copy that encrypted file to a safe place.

5. Delete the original wallet.dat file. (I won't lose anything right?)

Then when I need to spend, unencrypt the file and put it back into the roaming folder right?


Title: Re: Am I Encrypting Right?
Post by: bitlotto on June 20, 2011, 12:56:34 AM
Looks right. I don't know if I myself would use winrar though....
I'd recommend either truecrypt or gpg. Truecrypt would probably be the easiest to figure out. You create a "volume" that is pretty much a file. This file is "mounted" and makes it appear like a whole new drive on your computer. Copy the stuff to this new drive. Then "unmount". Copy that file you mounted.

But it's probably ok...


Title: Re: Am I Encrypting Right?
Post by: BombaUcigasa on June 20, 2011, 02:37:02 PM
Winrar
Wrong! This is not 1997, it's freaking 2011 you old gizzard!!!


Title: Re: Am I Encrypting Right?
Post by: MaGNeT on June 22, 2011, 05:30:42 AM
So...am I doing this right? What I did:

1. Turn off Bitcoin.

2. Copy the wallet.dat file.

3. I used Winrar to make an encryption.

4. Copy that encrypted file to a safe place.

5. Delete the original wallet.dat file. (I won't lose anything right?)

Then when I need to spend, unencrypt the file and put it back into the roaming folder right?


Don't forget to back-up the encrypted file to another location...
If your encrypted file fails, your BTC are gone forever...
If your memory fails to remember the password, your BTC are gone forever...


Title: Re: Am I Encrypting Right?
Post by: joan on June 22, 2011, 08:28:10 AM
4. Copy that encrypted file to a safe place.

5. Delete the original wallet.dat file. (I won't lose anything right?)
Try a restore before deleting the original.


Title: Re: Am I Encrypting Right?
Post by: jamesb on June 23, 2011, 12:04:20 PM
5. Delete the original wallet.dat file. (I won't lose anything right?)

Wrong too! If you don't erase the old file bytes on the hard drive it will be easily read again. You will have to use a secure random to overwrite the bytes if you want your deleted file to be unreadable forever (like shred on Unix)!


Title: Re: Am I Encrypting Right?
Post by: Oldminer on June 25, 2011, 11:44:43 AM

Wrong too! If you don't erase the old file bytes on the hard drive it will be easily read again. You will have to use a secure random to overwrite the bytes if you want your deleted file to be unreadable forever (like shred on Unix)!

Or you could just use www.encryptfiles.net

It gives you the option to delete or shred when you encrypt :)


Title: Re: Am I Encrypting Right?
Post by: BitCoinBarter on June 28, 2011, 12:47:24 AM

Or you could just use www.encryptfiles.net

It gives you the option to delete or shred when you encrypt :)

I would not use/goto www.encryptfiles.net

It has a bad rep on WOT. See http://www.mywot.com/en/scorecard/www.encryptfiles.net for details.


Title: Re: Am I Encrypting Right?
Post by: bitfreak! on June 28, 2011, 07:20:40 AM

Or you could just use www.encryptfiles.net

It gives you the option to delete or shred when you encrypt :)

I would not use/goto www.encryptfiles.net

It has a bad rep on WOT. See http://www.mywot.com/en/scorecard/www.encryptfiles.net for details.
That's because people seem to think it's a trojan due to warnings by their anti-virus software. I would guess they are simply false-positives due to the nature of the software. I don't think I've used it before though.


Title: Re: Am I Encrypting Right?
Post by: XIU on June 28, 2011, 11:29:28 PM
Winrar
Wrong! This is not 1997, it's freaking 2011 you old gizzard!!!

If you have v3 or higher, then it'll use AES 128bit, which given a long and strong password, should provide enough security.


Title: Re: Am I Encrypting Right?
Post by: unclemantis on July 27, 2012, 02:35:51 AM
Winrar
Wrong! This is not 1997, it's freaking 2011 you old gizzard!!!

If you have v3 or higher, then it'll use AES 128bit, which given a long and strong password, should provide enough security.

How long is overkill and how short is too short? I am using a paragraph of about 4 rather long sentences out of a book.


Title: Re: Am I Encrypting Right?
Post by: DeathAndTaxes on July 27, 2012, 02:46:49 AM
10 characters is generally immune to brute force attempts if the passphrase is not weak (not found in any dictionary, leaked password list, or common password database).  4 sentences is probably overkill although I would prefer a single sentence along with some numbers which have meaning to you so it is unlikely to be part of a precomputation database.


Title: Re: Am I Encrypting Right?
Post by: grue on July 27, 2012, 01:43:10 PM

Or you could just use www.encryptfiles.net

It gives you the option to delete or shred when you encrypt :)

I would not use/goto www.encryptfiles.net

It has a bad rep on WOT. See http://www.mywot.com/en/scorecard/www.encryptfiles.net for details.
>encryptfiles.net

seems legit 8)

That's because people seem to think it's a trojan due to warnings by their anti-virus software. I would guess they are simply false-positives due to the nature of the software. I don't think I've used it before though.
there's no possible reason why antivirus software will think encryption software would be a virus. after all, do you see winrar, 7zip, or truecrypt setting off alarms?


Title: Re: Am I Encrypting Right?
Post by: unclemantis on July 27, 2012, 05:55:33 PM
10 characters is generally immune to brute force attempts if the passphrase is not weak (not found in any dictionary, leaked password list, or common password database).  4 sentences is probably overkill although I would prefer a single sentence along with some numbers which have meaning to you so it is unlikely to be part of a precomputation database.

Is there a mask or set of rules that you apply when generating a 10 character passphrase?


Title: Re: Am I Encrypting Right?
Post by: Epoch on July 27, 2012, 06:10:10 PM
10 characters is generally immune to brute force attempts if the passphrase is not weak (not found in any dictionary, leaked password list, or common password database).  4 sentences is probably overkill although I would prefer a single sentence along with some numbers which have meaning to you so it is unlikely to be part of a precomputation database.
Is there a mask or set of rules that you apply when generating a 10 character passphrase?

First off, here is an informative (old but still mostly relevant) article describing password cracking ('recovery' is the politically-correct term) with GPUs and commercially available cracking software:

http://www.tomshardware.com/reviews/password-recovery-gpu,2945.html (http://www.tomshardware.com/reviews/password-recovery-gpu,2945.html)

TLDR:

1) At least ten characters in length.
2) Contain at least one upper-case letter
3) Contain at least one lower-case letter
4) Contain at least one special character, such as @ or !
5) Contain at least one number

The idea being to force any brute-force attack to search a large portion of the ASCII space, essentially increasing the 'strength' of each character of your password compared to, say, using lower- and upper- case letters only.


Title: Re: Am I Encrypting Right?
Post by: Deafboy on July 27, 2012, 06:39:55 PM
In my .bitcoin directory, there is only link to wallet.dat on USB. So there is no need to delete anything on local HDD after closing bitcon client. I just unplug the USB key.
Also I keep several online and offline backups of wallet in truecrypt containers, and several backups of keepassx password database with password for truecrypt containers and wallet itself.


Title: Re: Am I Encrypting Right?
Post by: bluefirecorp on July 27, 2012, 09:36:09 PM
10 characters is generally immune to brute force attempts if the passphrase is not weak (not found in any dictionary, leaked password list, or common password database).  4 sentences is probably overkill although I would prefer a single sentence along with some numbers which have meaning to you so it is unlikely to be part of a precomputation database.
Is there a mask or set of rules that you apply when generating a 10 character passphrase?

First off, here is an informative (old but still mostly relevant) article describing password cracking ('recovery' is the politically-correct term) with GPUs and commercially available cracking software:

http://www.tomshardware.com/reviews/password-recovery-gpu,2945.html (http://www.tomshardware.com/reviews/password-recovery-gpu,2945.html)

TLDR:

1) At least ten characters in length.
2) Contain at least one upper-case letter
3) Contain at least one lower-case letter
4) Contain at least one special character, such as @ or !
5) Contain at least one number

The idea being to force any brute-force attack to search a large portion of the ASCII space, essentially increasing the 'strength' of each character of your password compared to, say, using lower- and upper- case letters only.
http://imgs.xkcd.com/comics/password_strength.png


Title: Re: Am I Encrypting Right?
Post by: unclemantis on July 27, 2012, 10:12:54 PM
10 characters is generally immune to brute force attempts if the passphrase is not weak (not found in any dictionary, leaked password list, or common password database).  4 sentences is probably overkill although I would prefer a single sentence along with some numbers which have meaning to you so it is unlikely to be part of a precomputation database.
Is there a mask or set of rules that you apply when generating a 10 character passphrase?

First off, here is an informative (old but still mostly relevant) article describing password cracking ('recovery' is the politically-correct term) with GPUs and commercially available cracking software:

http://www.tomshardware.com/reviews/password-recovery-gpu,2945.html (http://www.tomshardware.com/reviews/password-recovery-gpu,2945.html)

TLDR:

1) At least ten characters in length.
2) Contain at least one upper-case letter
3) Contain at least one lower-case letter
4) Contain at least one special character, such as @ or !
5) Contain at least one number

The idea being to force any brute-force attack to search a large portion of the ASCII space, essentially increasing the 'strength' of each character of your password compared to, say, using lower- and upper- case letters only.
http://imgs.xkcd.com/comics/password_strength.png

Doesn't 4 words go against the rules of having a dictionary word?


Title: Re: Am I Encrypting Right?
Post by: P_Shep on July 27, 2012, 10:42:35 PM
Doesn't 4 words go against the rules of having a dictionary word?

No, as it's 4 of them.

No. words in dictionary * No. words in dictionary * No. words in dictionary * No. words in dictionary = big number


Title: Re: Am I Encrypting Right?
Post by: unclemantis on July 28, 2012, 05:30:49 AM
Doesn't 4 words go against the rules of having a dictionary word?

No, as it's 4 of them.

No. words in dictionary * No. words in dictionary * No. words in dictionary * No. words in dictionary = big number

Gotcha.

Well I guess I am reencrypting my wallet tomorrow :-D And then going around and picking up all the backups. Shreeding them and then redistributing the new one LOL