<p>Turning off RPC will prevent that particular attack vector, but if the coins are on a machine connected to the internet, that's a lot of vulnerabilities and attack vectors to consider.</p>

<p>That said, if you're running a node on EC2, you're not going to generate enough bitcoins to be worth stealing. If the point is to figure out how everything works, I wouldn't worry about the bitcoins you'll be mining since it'll be so little (at most $10 per year).</p>

CC BY-SA 3.0
2015-03-10T02:16:55.993Z
I'm not interested in the money but I *am* interested in the security considerations. Could you elaborate on some of the vulnerabilities/attack vectors you mention?
ConstableJoe
CC BY-SA 3.0
2015-03-10T02:13:59.803Z
2015-03-10T02:13:59.803Z
Jimmy Song
<p>Whether bitcoind is accepting RPC calls has very little bearing on whether it's secure. By default, bitcoind only accepts connections originating from the local computer. In most situations where an attacker can make connections to RPC, they would have the ability to look in your wallet folder and copy your wallet off. (There are a bunch of tricky exceptions to that. For example, it's possible to take away a user's SSH privileges without taking away their ability to use SSH port forwarding.)</p>

<p>Additionally, if you turn on RPC, bitcoin will generate a password for it which is too long to be guessed. (This password is different from wallet encryption.)</p>

<p>If your wallet <em>was</em> encrypted, then you wouldn't be able to use a cron script to automatically transfer your Bitcoins to your exchange account.</p>

<p>I would call leaving your wallet unencrypted an acceptable security risk.</p>

CC BY-SA 3.0
2015-03-10T09:16:09.500Z
2015-03-10T09:16:09.500Z
Nick ODell
<p>I'm interested in setting up a <a href="http://p2pool.org/" rel="nofollow">P2Pool node</a> (which requires running <code>bitcoind</code>) to run a little mining pool for myself. Before you ask, nope I'm not even trying to break even, I know I'll lose money on this. Just want to play around and get a feel for how these things work.</p>

<p>My question is: I hear over and over again that it's important to take security precautions with <code>bitcoind</code> and wallets, but I've had trouble teasing out exactly what those security precautions are. If I have <code>bitcoind</code> not accepting RPC calls (as is the default), is there any danger to using the out-of-the-box unencrypted wallet?</p>

<p>If the information helps, I'll probably run the node in EC2, and have a cron job that frequently transfers any bitcoins earned through mining into an account in an exchange so I can play around with that side of things as well (so I'm not worried about large sums of bitcoin building up in my <code>bitcoind</code> wallet).</p>

CC BY-SA 3.0
2015-03-10T01:39:10.313Z
Thanks for the edit; my question clarified itself as I was writing it and I forgot to change the title. :)
ConstableJoe
<transactions><wallet><bitcoind><security><wallet-security>
Is an unencrypted wallet secure if bitcoind is not accepting RPC calls?
ConstableJoe
# Is an unencrypted wallet secure if bitcoind is not accepting RPC calls?

(Asked by: username_0 on 2015-03-10)

I'm interested in setting up a [P2Pool node](http://p2pool.org/) (which requires running `bitcoind`) to run a little mining pool for myself. Before you ask, nope I'm not even trying to break even, I know I'll lose money on this. Just want to play around and get a feel for how these things work.

My question is: I hear over and over again that it's important to take security precautions with `bitcoind` and wallets, but I've had trouble teasing out exactly what those security precautions are. If I have `bitcoind` not accepting RPC calls (as is the default), is there any danger to using the out-of-the-box unencrypted wallet?

If the information helps, I'll probably run the node in EC2, and have a cron job that frequently transfers any bitcoins earned through mining into an account in an exchange so I can play around with that side of things as well (so I'm not worried about large sums of bitcoin building up in my `bitcoind` wallet).

**Tags:** transactions, wallet, bitcoind, security, wallet-security

> **Comments:**
> **username_0**: Thanks for the edit; my question clarified itself as I was writing it and I forgot to change the title. :)  

---

## 2 answers

### Answer by username_1 on 2015-03-10. Score: 1

Turning off RPC will prevent that particular attack vector, but if the coins are on a machine connected to the internet, that's a lot of vulnerabilities and attack vectors to consider.

That said, if you're running a node on EC2, you're not going to generate enough bitcoins to be worth stealing. If the point is to figure out how everything works, I wouldn't worry about the bitcoins you'll be mining since it'll be so little (at most $10 per year).

> **Comments:**
> **username_0**: I'm not interested in the money but I *am* interested in the security considerations. Could you elaborate on some of the vulnerabilities/attack vectors you mention?  

---

### Answer by username_2 on 2015-03-10. Score: 0

Whether bitcoind is accepting RPC calls has very little bearing on whether it's secure. By default, bitcoind only accepts connections originating from the local computer. In most situations where an attacker can make connections to RPC, they would have the ability to look in your wallet folder and copy your wallet off. (There are a bunch of tricky exceptions to that. For example, it's possible to take away a user's SSH privileges without taking away their ability to use SSH port forwarding.)

Additionally, if you turn on RPC, bitcoin will generate a password for it which is too long to be guessed. (This password is different from wallet encryption.)

If your wallet *was* encrypted, then you wouldn't be able to use a cron script to automatically transfer your Bitcoins to your exchange account.

I would call leaving your wallet unencrypted an acceptable security risk.


---

