Introduce newer auth options

[unsystemizer]

Spotted in Bitcoin Core 0.12.1 log:

2016-05-23 14:10:29 Config options rpcuser and rpcpassword will soon be deprecated. \
Locally-run instances may remove rpcuser to use cookie-based auth, or may be replaced \
with rpcauth. Please see share/rpcuser for rpcauth auth generation.

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/34494634-introduce-newer-auth-options?utm_campaign=plugin&utm_content=tracker%2F494308&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F494308&utm_medium=issues&utm_source=github).

[unsystemizer]

Took another look at this:

• Bitcoin Core ships a passgen script (https://github.com/btcdrak/bitcoin/tree/v0.12.1-addrindex/share/rpcuser) that we could run to generate this password, but...
• The deterministically built binaries don't contain that script

I guess we should decide whether we want to do nothing, go back to build-on-demand in run.py, or do something else (e.g. include the script in run.py or link it from our repo)..

Cookie-based auth is interesting.

Thoughts?

Related Bitcoin Core commit: https://github.com/bitcoin/bitcoin/commit/f04f4fd2eed581a5e287d14036d790cf2badcbe6

[unsystemizer]

0.13.2 addrindex contains the script - https://github.com/btcdrak/bitcoin/tree/addrindex-0.13/share/rpcuser

[unsystemizer]

I tried this using the bundled rpcuser.py script and counterparty-client/-server didn't have any issues with this approach.

$ python2 rpcuser.py rpc
String to be appended to bitcoin.conf:
rpcauth=rpc:525d39cda3c923ddedee82a532b044fe$dedc672ee7b098654c3f332b2562d982577715169c7523596880e7da8a3a7b52
Your password:
HhVjSAf-RIv_3ATBU6xlhYUU1iCSYJXJ57ZCmiNYPOI=