All HTTPS-JSON-RPC-related bitcoin.conf options:
rpcport : default: 8332 Listen for connections on this port
rpcuser : user for HTTP BASIC authentication
rpcpassword : password for HTTP BASIC authentication
rpcssl : Not set by default, if set bitcoin will only accept SSL
rpcallowip : Allow a client at this IP address to connect
(may be specified multiple times)
rpcsslciphers: default "TLSv1+HIGH:!SSLv2:!aNULL:!eNULL:!AH:!3DES:@STRENGTH"
(see the openSSL documentation for syntax)
rpcsslcertificatechainfile : default "server.cert"
rpcsslprivatekeyfile : default "server.pem"
I think we should go ahead and add client authentication by SSL.
Need rpcsslcacertificates and rpcsslcarevoked variables. Moreover, it is best to add the ability read them directly from the directory in the set.
Then the next logical step is to add to a demon simultaneous control of several wallets.
The result is a ready infrastructure for the secure storage of money for a group of people in the likeness of mybitcoin.
These people have their low-power mobile devices (with client like this: https://bitcointalksearch.org/topic/working-android-app-533 ) will be able to securely connect to that server and send and receive money.
Huh... And so bitcoin captures the Universe!..