Bitcoin Forum
June 22, 2017, 08:44:04 PM *
News: Latest stable version of Bitcoin Core: 0.14.2  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 [19] 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 ... 129 »
  Print  
Author Topic: HOWTO: create a 100% secure wallet  (Read 259776 times)
btcontilt
Jr. Member
*
Offline Offline

Activity: 53


View Profile WWW
July 19, 2011, 04:50:44 PM
 #361

thanks nice post

bitcoin poker www.btcontilt.com
1498164244
Hero Member
*
Offline Offline

Posts: 1498164244

View Profile Personal Message (Offline)

Ignore
1498164244
Reply with quote  #2

1498164244
Report to moderator
1498164244
Hero Member
*
Offline Offline

Posts: 1498164244

View Profile Personal Message (Offline)

Ignore
1498164244
Reply with quote  #2

1498164244
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1498164244
Hero Member
*
Offline Offline

Posts: 1498164244

View Profile Personal Message (Offline)

Ignore
1498164244
Reply with quote  #2

1498164244
Report to moderator
riceberry
Hero Member
*****
Offline Offline

Activity: 592



View Profile
July 19, 2011, 06:27:00 PM
 #362

I used truecrypt before, but I like this solution here

http://bitcoin.blog.com/2011/07/17/linux-bitcoin-wallet-encryption/

uses seahorse-tool, with a custom startup script to decrypt as you open bitcoin, then ecrypt again when closing.
also back up a copy of your encrypted wallet and put it somewhere safe

btcking
Newbie
*
Offline Offline

Activity: 5


View Profile
July 19, 2011, 11:43:26 PM
 #363

Thanks. I always encrypt my wallet and also copy it to several locations that are not on my hard drive I pulled it from
Bubi
Newbie
*
Offline Offline

Activity: 3


View Profile
July 20, 2011, 09:00:07 AM
 #364

Thanks for the advice, you can never be too safe when dealing with money Smiley.
Fountainhead
Newbie
*
Offline Offline

Activity: 5


View Profile
July 20, 2011, 01:38:21 PM
 #365

Paper money --> more secure than bitcoin
bigb159
Full Member
***
Offline Offline

Activity: 169



View Profile
July 20, 2011, 02:42:00 PM
 #366

Paper money --> more secure than bitcoin

Don't you have mattresses to stuff? I just backed my wallet up to dropbox. I can be pretty dumb.

Trade your Litecoin, Namecoin, Terracoin, Devcoin and IXcoin for Bitcoin: Vircurex
Coin to Bux
Newbie
*
Offline Offline

Activity: 5


View Profile
July 20, 2011, 03:32:39 PM
 #367

nice guiod
ngr
Newbie
*
Offline Offline

Activity: 5


View Profile
July 21, 2011, 12:54:23 AM
 #368

Good guide, something everyone should give a read before they realize how easy wallets can be compromised.
netrin
Sr. Member
****
Offline Offline

Activity: 322


FirstBits: 168Bc


View Profile
July 21, 2011, 02:02:57 AM
 #369

why doesn't the client have built in encryption for wallets? Is that not something the community thinks is important enough to include?

The client is still alpha software. It's coming.

Greenlandic tupilak. Hand carved, traditional cursed bone figures. Sorry, polar bear, walrus and human remains not available for export.
bionicghost
Member
**
Offline Offline

Activity: 88


GaoGaiGar!


View Profile
July 21, 2011, 02:04:24 AM
 #370

Is there a way i can save the current block list alongside the wallet file, so that i don't have to wait increasingly longer periods of time waiting for it to download entirely each and every time i decide to use my safe wallet?

Edit- Ok, that was already answered, appearently, so i'll rephrase: what filename does the block list has?

COURAGE WILL NEVER DIE!

12YstBn86ysRCrHx4qRBbfVhqoFCLENr77
ewarrior
Newbie
*
Offline Offline

Activity: 7


View Profile
July 21, 2011, 03:44:33 AM
 #371

thanks great guide
netrin
Sr. Member
****
Offline Offline

Activity: 322


FirstBits: 168Bc


View Profile
July 21, 2011, 06:12:01 PM
 #372

Is there a way i can save the current block list alongside the wallet file, so that i don't have to wait increasingly longer periods of time waiting for it to download entirely each and every time i decide to use my safe wallet?

Edit- Ok, that was already answered, appearently, so i'll rephrase: what filename does the block list has?

Generally the *dat files exclusive wallet.dat. But with every client release (and patches) there seems to be consolidation along with new scattered files. If you switch wallets, --rescan, and send transactions, the following files/directories will likely change:

blk000*.dat
blkindex.dat
database/
__db.00*
debug.log

addr.dat
wallet.dat

There is not a clean separation between private, public, and temp/log data. Even wallet.dat contains many references to public data, such as the earliest relevant block. Though little if any public data makes identifying references to the wallet.dat.

Greenlandic tupilak. Hand carved, traditional cursed bone figures. Sorry, polar bear, walrus and human remains not available for export.
kermitscott
Newbie
*
Offline Offline

Activity: 2


View Profile
July 21, 2011, 07:02:34 PM
 #373

I'm beginning to understand!
epiks
Member
**
Offline Offline

Activity: 84


View Profile
July 21, 2011, 07:40:05 PM
 #374

cant ppl still steal your wallet by emailing it to themselves then just loading up your wallet with their bitcoin program? you wont even have to open it or attempt to read it
Neokolzia
Newbie
*
Offline Offline

Activity: 14


View Profile
July 22, 2011, 07:08:25 AM
 #375

Through building my rigs I've made like 5 other orders after the initial order for the rig, Dummy plugs, KVM Switches... and not to mention now a decent 16GB USB drive that is going to be exactly this. Love the guide thank u.
Nobu
Newbie
*
Offline Offline

Activity: 15


View Profile
July 22, 2011, 02:59:17 PM
 #376

cant ppl still steal your wallet by emailing it to themselves then just loading up your wallet with their bitcoin program? you wont even have to open it or attempt to read it

Only if they know where it is and have access to it--access being:
1.) Remote, through insecure SSH configuration, lax network share permissions, etc..
2.) Local, via an insecure account (bad password/lax permissions)
3.) Local, by taking the physical hard drive from the machine.

(1) can be avoided by keeping the machine you store your key on off of your local network and the internet, or by keeping your wallet on a removable disk/drive (and never allowing the file to touch other drives). (2) can be avoided by keeping your local user accounts secure, or by keeping the wallet on a removable(...). (3) can be avoided by keeping the file on a secure media in a secure place as with (1) and (2). (1), (2), and (3) can all be mitigated by encryption, but if a thief has your wallet (even if it's encrypted) then he only needs to crack the encryption (which will take a while) and he has your coin.

To prevent a thief who has somehow procured your ("secure") bank wallet from getting your coin, you may choose to make a new secure wallet every now and then (and transfer the funds from the old wallet to the new one). With encryption, that should be enough to prevent a thief from getting anything before you can say "Peter piper picked a peck of pickled peppers". It's up to you how long between new wallets you want to go, but I don't think you need to do it too often.

The most important point to remember is that if your (encrypted or not) wallet is ever on a non-encrypted storage medium, then it's data will remain there for anyone to scrape if they have physical access to the drive (and sometimes even without), until that data is replaced (which may take a while, unless you shred it, but it still may be there depending on the filesystem you're using). So if you can keep the wallet encrypted throughout it's entire lifetime, that would be best (particularly if it's also on a fully encrypted volume), and if you can keep it from touching your hard-drive until it can be encrypted that's good too.

Donations, tips: 1Ac4ERXJoQbLrgaTCphrFtcFiExGkfEYNZ
XMPP IM: Nobu@jabber.org
Mining "rig": cgminer on an Athlon64 X2 2Ghz, ~1.8MHash/s
infogulch
Newbie
*
Offline Offline

Activity: 3


View Profile
July 22, 2011, 08:07:26 PM
 #377

1. Boot to live CD
2. Use bitcoin to generate your wallet.dat and however many keys you want.
3. Extract the public AND private keys (well, when they finally merge the PULL request on github)
    3a. on a separate sd card, store all your public keys so you can get to them later
4. PRINT the keys out on your printer, and leave some extra space and use a pen to copy them down again (printer ink can fade over years)
5. Put the keys in a security envelope, and then in a tamper-evident manila envelope.
6. Go get a 2"x5" safety deposit box at your local bank for $10/yr and put the envelope in there.
    6a. (optional) include a small sd card with the wallet.dat and plaintext keys so it's easier than importing keys manually
7. Don't forget to pay the annual lease for the SD box (perhaps pay several years in advance?)
8. Huh
9. PROFIT

1MZ9VikkRfziY8zGSDwDPBZJzmGiYXckey
piramida
Legendary
*
Offline Offline

Activity: 1106



View Profile
July 22, 2011, 09:56:26 PM
 #378

Dept. of Defence releases a tiny secure linux distro, USB bootable, what else you need for the secure wallet Smiley http://www.geek.com/articles/chips/u-s-dept-of-defense-offers-up-tiny-secure-linux-distribution-20110722/

i am satoshi
ganalon
Jr. Member
*
Offline Offline

Activity: 34



View Profile WWW
July 23, 2011, 12:00:59 AM
 #379

Thanks.  I think I like the vault/safety-deposit-box approach with redundant copies.

Ganalon -- Techie and Financial Guy
http://websqurl.com/
cdnadvis
Newbie
*
Offline Offline

Activity: 10


View Profile
July 23, 2011, 02:20:21 AM
 #380

Thanks this is a big help
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 [19] 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 ... 129 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!