![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
April 19, 2013, 01:16:48 PM |
|
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?
|