password protected wallet with bitcoind

[rupy]

Will there be a password property on the JSON API to send money?

I mean to host the bitcoind on AWS EC2, which implies I need some kind of encryption if people are to trust this setup, how do other pool operators manage this?

[Revalin]

Yes, you can use walletpassphrase to unlock the wallet, send the coins, then relock the wallet.

Why are you doing this though?  You haven't added much security if the script which unlocks the wallet is on the same server.  If the script is on another server, why not just sen the coins from there?

[rupy]

I will load the password from a remote location encrypted into the web server memory so it will be VERY hard for any amazon employee or anyone else to steal the wallet.

[rupy]

Ok, I did some additional thinking around this, so this is how you would do it?

1) walletpassphrase (1 sec.)
2) sendtoaddress
3) walletlock

The scenario here is to have a bitcoind running with HTTPS on a server that is outside of my physical control.

The client software would be on the same machine, and the password would only be stored encrypted (with a custom encryption) in the memory of the client software, fetched over HTTPS when the client is started from a secure location _under_ my physical control and only available when I start the client.

Is this how pool owners do it?

[rupy]

But I also just figured that you can't steal bitcoins, because you cannot spend stolen bitcoins EVER!