wallet.dat and bitcoind | Bitcointalksearch.org

cronopio

newbie

Activity: 55

Merit: 0

Quote from: DamienBlack on June 18, 2011, 04:57:51 AM

Please visit

https://github.com/bitcoin/bitcoin/pull/232

To see what the developers are doing about encryption. The developers are already very far along. Any discussion should be held there.

+1 Thanks for the link to the issue

DamienBlack

jr. member

Activity: 56

Merit: 1

Please visit

https://github.com/bitcoin/bitcoin/pull/232

To see what the developers are doing about encryption. The developers are already very far along. Any discussion should be held there.

Shevek

sr. member

Activity: 252

Merit: 250

After the last wallet steal, there is a strong recommendation to protect wallet.dat from trojans.

I think one of the worst weakness of the actual development of bitcoin, is the mixing of client and server/daemon activities. AFAIK, the daemon does not need anyway the file "wallet.dat".

So, I propose to separate both programs definitively. "Bitcoind" should have the data (except "wallet.dat") in ~.bitcoind directory. And "bitcoin" should have its own, let's say, ~.bitcoin directory with encrypted "wallet.dat".

If the user has an active "bitcoind" daemon, "bitcoin" searches in ~.bitcoind the data for RCP-connection to the daemon. Eventually, "bitcoin" can connect to a remote "bitcoind" and then the program should ask for data connection, which eventually can also be hosted on ~.bitcoin.

Topic: wallet.dat and bitcoind (Read 1063 times)