...
| Tip |
|---|
The Bitcoin Core node (bitcoind) is now running.
|
...
5. Setup a secure tunnel for
...
The tunnel must be live 24x7.
...
encrypted communication.
Your CAS server and this node must have a secure line. Your passphrase and other sensitive information will be passed back & forth. Encrypt (and protect) this communication by using a secure SSH tunnel.
The GB Wallet Tunnel is recommended.
General Bytes has incorporated an open-source ssh SSH client into CAS.
Click here for instructions to install the GB Wallet Tunnel Server .
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:
You may elect to use a SSH tunnel for secure RPC communication with the node. We also discourage running any software on your CAS server (except for CAS itself) and this includes Bitcoin Core. The solution is use port forwarding to enable access to your separate Bitcoin Core node. We recommend "dialing out" from CAS to the node. Seeon this node.
Alternative (unsupported):
Build an SSH tunnel (instead of the GB Wallet Tunnel), see: https://generalbytes.atlassian.net/
...
...
The general usage would be:
| Code Block |
|---|
ssh -f -N -i /home/gb/.ssh/bitcoind -L 8332:127.0.0.1:8332 gb@35.237.163.176 |
In the above example,
"ssh -f -N" is the "create a permanent tunnel in the background" command.
"-i /home/gb/.ssh/bitcoind" specifies the private SSH key to be used.
"-L 8332:127.0.0.1:8332" are the node's RPC port definitions.
"gb@35.237.163.176" is the SSH "dial-in" identity of the node.
...
For those instructions, set
FORWARDED_PORT=8332
...
6. Save the required information for CAS:
...