<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
<channel>
<title>MultiChain Developer Q&amp;A - Recent questions tagged password</title>
<link>https://www.multichain.com/qa/tag/password</link>
<description>Powered by Question2Answer</description>
<item>
<title>Fail to authorize in multichain-cli after change the datadir.</title>
<link>https://www.multichain.com/qa/2345/fail-to-authorize-in-multichain-cli-after-change-the-datadir</link>
<description>I created my first test chain and it worked fine. But I found the data is located in my home folder which has limited disk space. so I stopped the multichaind and removed the existing data folder, then updated the multichain.conf in ~/.multichain/multichain.conf to setup the new datadir. Then I created the new chain with same name, edited the params in the new location and started the multichaind in daemon mode.&lt;br /&gt;
&lt;br /&gt;
Everything looks fine except:&lt;br /&gt;
&lt;br /&gt;
I tried to access my chain throgh multichain-cli but keeps getting the authorization fail error.&lt;br /&gt;
&lt;br /&gt;
What is the default rpcusername and password and how can I change it? The password seems secured.&lt;br /&gt;
&lt;br /&gt;
I did found the multichain.conf in the datadir and it shows&lt;br /&gt;
&lt;br /&gt;
================================================&lt;br /&gt;
&lt;br /&gt;
rpcuser=multichainrpc&lt;br /&gt;
rpcpassword=4neAQb2V9Q6ZVYkMPBFcGg5ZUKMP1ub6BH4qDD21cJQk&lt;br /&gt;
&lt;br /&gt;
================================================&lt;br /&gt;
&lt;br /&gt;
My operation and response are&lt;br /&gt;
&lt;br /&gt;
================================================&lt;br /&gt;
&lt;br /&gt;
# multichain-cli -datadir='/main/multichain' GooCoinTest&lt;br /&gt;
&lt;br /&gt;
MultiChain Core RPC client build 1.0 alpha 22 protocol 10005&lt;br /&gt;
&lt;br /&gt;
Interactive mode&lt;br /&gt;
&lt;br /&gt;
GooCoinTest: help&lt;br /&gt;
{&amp;quot;method&amp;quot;:&amp;quot;help&amp;quot;,&amp;quot;params&amp;quot;:[],&amp;quot;id&amp;quot;:1,&amp;quot;chain_name&amp;quot;:&amp;quot;GooCoinTest&amp;quot;}&lt;br /&gt;
&lt;br /&gt;
error: incorrect rpcuser or rpcpassword (authorization failed)&lt;br /&gt;
&lt;br /&gt;
================================================</description>
<guid isPermaLink="true">https://www.multichain.com/qa/2345/fail-to-authorize-in-multichain-cli-after-change-the-datadir</guid>
<pubDate>Wed, 03 Aug 2016 20:42:27 +0000</pubDate>
</item>
<item>
<title>Alternative to unlocking an encrypted wallet</title>
<link>https://www.multichain.com/qa/173/alternative-to-unlocking-an-encrypted-wallet</link>
<description>Sorry - I know that this is Q&amp;amp;A, but I can't find an appropriate place for feature requests, so here goes...&lt;br /&gt;
&lt;br /&gt;
Unlocking the wallet for a period of time is one of the biggest security flaws with the bitcoin daemon. Once the wallet is unlocked then any process on an authorised machine can connect and issue send instructions until such stage as the wallet is locked again.&lt;br /&gt;
&lt;br /&gt;
Just a thought, but how about appending the wallet password as an optional parameter to the JSON RPC calls that require an encrypted wallet to be unlocked. Assuming the implementation used SSL for RPC calls the password can be transmitted to the daemon securely and used to unlock it solely for that method call.</description>
<guid isPermaLink="true">https://www.multichain.com/qa/173/alternative-to-unlocking-an-encrypted-wallet</guid>
<pubDate>Tue, 29 Sep 2015 11:54:53 +0000</pubDate>
</item>
</channel>
</rss>