Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Save all the information securely. You'll need every detail in the steps to follow.  

  • The RPC User = AnyNameYouWantHere

  • The RPC Password = Kq66rZya7MNpCU_e0zZSgjR2Mb7rBeyX9QSeGhwPMeY=

  • The cookie/token ("rpcauth") will only be required in the Bitcoin Core configuration file (next step).

Tip

The RPC Password is required for CAS - noted in Step 6.

The cookie/token is a secure hash of your password. The point is to hide your password on the node server to other users of the node. If your node is secure, then using the cookie is simply added security in the event of a server breach, however if your server is breached - you have a bigger problem than an exposed password - and that hash will afford very little protection.

The password is sent to the RPC server software by CAS, and must be kept encrypted while traveling over the Internet. This is accomplished using “tunnels”.

...

3. Create the Bitcoin Core configuration file.

...

Code Block
server=1
daemon=1
addresstype=legacy
rpcport=8332
rpcauth=ThisIsAnExample:77cf8c03b15219cafb1e72ae9329d5fd$72de450660cdb6dd2689cd2cba4091646a5e8005490dec07dc577b6dad67770e
  • Replace the “rpcauth” line with the cookie/token you generated in the previous step.

  • Exit the nano editor with Control+X and save your changes.

  • The CAS parameter “port” is the same as the “rpcport” specified in this step.

...

4. Start the bitcoind daemon:

...

Click here for instructions to install the GB Wallet Tunnel Server.

  • Perfect for the GB Cloud.

  • The CAS “host” parameter used will be this node’s public IP.

  • The CAS “port” parameter will be the same port specified as the “rpcport” in Step 3 (above).

Option 2: Creating an SSH tunnel:

...