📌 Purpose & Quick Summary

For developers who prefer working in desktop IDEs (such as VS Code Remote SSH) or terminal emulators (PuTTY, iTerm2, Windows Terminal), the SSH Credentials tab allows you to configure shell access passwords and install public SSH keys (authorized_keys) for passwordless, cryptographically secure authentication.

BoostonCP SSH Credentials & Key Management

Figure 14.1: SSH credentials and public key management interface showing host, port, and key installer.


🖥️ Interface Tour & Elements

  1. Connection Credentials Card: Displays Hostname, IP address, SSH Port (e.g. 22 or custom), and Linux Username.
  2. Password Unlock & Rotation: Allows setting or rotating a strong SSH password, or clearing the password to enforce SSH-key-only authentication.
  3. Public Key Management: Input area to paste your id_rsa.pub or id_ed25519.pub public key string.

🛠️ Step-by-Step Instructions

Step 1: Adding Your Public SSH Key

  1. Navigate to Terminal and click the SSH tab.
  2. In the Authorized Keys section, click Add Public Key.
  3. Open your local terminal on your PC and copy your public key:
    cat ~/.ssh/id_ed25519.pub
  4. Paste the key string (ssh-ed25519 AAAA... user@local) into the textarea.
  5. Click Install Key. The key is appended to your /home/user/.ssh/authorized_keys with 0600 permissions.

Step 2: Connecting via Local Terminal

  1. Open your computer's terminal and execute:
    ssh -p 22 [email protected]
  2. The server verifies your cryptographic key and opens a shell session immediately without requesting a password.

⚙️ Complete Field & Parameter Reference Table

Connection Parameter Value Security Impact
Host Domain or Server IP Remote SSH server endpoint.
Port 22 (or custom admin port) Configured SSH daemon listener port.
Supported Key Types ed25519, RSA (3072+) ED25519 recommended for highest cryptographic strength and performance.
Key Enforcement Optional Disabling password auth prevents brute-force login attacks completely.

❓ Troubleshooting & Common Errors

1. Connection Refused: "Permission denied (publickey)"

  • Cause: Your private key does not match the public key installed in the panel, or permissions on ~/.ssh were changed.
  • Solution: Ensure your private key matches the installed public key. Re-paste the public key in the SSH tab and click Install Key.