Quilibrium.one
SocialOfficial
Quilibrium Node Guide
Quilibrium Node Guide
  • 🖖Introduction
  • ✅Safety checks
  • đŸ“ŖAnnouncements
  • 🔗Links & Info
  • đŸ’ģBest server providers
  • đŸ’ģHardware requirements
  • 😎Q1 - Node Manager
  • ⚡Node Auto-installer
  • âŦ†ī¸Updating your node
  • âœ”ī¸Check your node info
  • 🔑Backup your private keys
  • đŸ“ĻBackup your node
  • 🔁Set up the gRPC calls
  • đŸ› ī¸Tools and scripts
  • 🔧Extra tools
  • 🔠Useful commands
  • â‰ī¸Troubleshooting
  • 📌Tutorials
    • Node
      • đŸ”ĸNode step by step installation
      • đŸŗInstalling the node on Docker
      • đŸĒŸInstalling the node and the qclient on Windows WSL
      • â†—ī¸Migrating the node to a new server
      • â„šī¸Running the node via binary file
      • Running a node cluster
      • ✅Reinstalling the node from scratch
      • âš™ī¸Managing your system resources
        • â˜‘ī¸Limiting your vCores usage
        • â˜‘ī¸Limiting your CPU usage
        • â˜‘ī¸Limiting the RAM assigned to each vCore
      • 🔄Switching from tmux to service
      • 💲Log your node balance every 1 hour
      • 🩷Escaping the "Pink Screen of Death"
      • 🔒Set up SSH keys
      • 🔒Creating a root login access
      • 👀Renting Servers Unveiled: Exploring Types and Processor Terminology
    • Qclient
      • Qclient commands
      • How to transfer QUIL
      • How to Bridge QUIL to WQUIL
      • How to retrieve your coin address after a failed bridging operation
  • 📂Archive
    • ⚡OLD - Node Auto-installer
    • đŸ”ĸOLD - Node step by step installation
    • 🔠OLD - Useful server commands
    • â‰ī¸OLD Troubleshooting
    • âŦ†ī¸OLD Updating your node
    • ⚡Importing an existing store folder for fast sync
    • â˜‘ī¸Changing the cpulimit value in release_autorun
  • âš ī¸Work in progress
  • 💜Want to say thank you?
Powered by GitBook
On this page
  1. Tutorials
  2. Node

Set up SSH keys

PreviousEscaping the "Pink Screen of Death"NextCreating a root login access

Last updated 1 month ago

Usually, when you rent a server, you are given a username and password to connect to it. However, this poses a security risk as hackers can attempt to guess your password using brute force attacks. To mitigate this risk, you can disable password access to your server and use SSH keys instead.

My personal way is to set up just one pair of keys: the private key resides on the local PC and the public key on any server I want to access. If I use more than one local device to access my servers, I set up another key pair for each new device.

Here is a on how to set up SSH keys on your server.

Alternatively, you can use Termius, which offers a simpler method as outlined below:

  1. Install and follow to generate an SSH key. Remember to securely store your key, either in an encrypted folder on your computer or on an encrypted USB drive.

  2. Through Termius, you can easily export the SSH key to your host and create an identity as explained in the guide.

  3. Test that you can successfully connect to the server using this SSH key.

  4. If you have multiple nodes or servers, you can use the same SSH key for all of them.

  5. Once logged into your server, run sudo nano /etc/ssh/sshd_config.

  6. Scroll down using the down arrow until you locate the line # PasswordAuthentication yes. Uncomment the line (remove #) and set it to no, like so: PasswordAuthentication no.

  7. To save the changes, press CTRL+X, then Y, then ENTER.

  8. Restart your SSH service by running sudo systemctl restart ssh.

Now, you should only be able to access the server via SSH key, and password-based access will no longer work.


📌
🔒
comprehensive guide
Termius
this guide
Cover

Want to say thank you?

CLICK TO DONATE