I would suggest adjusting the firewall rule to only allow ssh from your specific IP.
For example:
sudo ufw allow from 15.15.15.15/32 to any port 22
You are viewing a single comment's thread from:
I would suggest adjusting the firewall rule to only allow ssh from your specific IP.
For example:
sudo ufw allow from 15.15.15.15/32 to any port 22
Also, after unlocking the wallet the bash history should be cleared so that the pwd can't be found if the box is compromised. The wallet should also be locked too shouldn't it at some point?
cat /dev/null > ~/.bash_history && history -c && exitHey Steve, I was trying to add these suggestions, but looks like I can no longer edit my post. These are good suggestions, and I hope future readers of this will scroll down and see this.
As for locking the wallet after the MN has started, I think we can solve this by lowering the expiration on the walletpassphrase command to something like 600 seconds, which means the wallet will lock after 600 seconds have passed:
Lindad walletpassphrase "the password you set above" 600