Fill the Server: 80% off your first 4 monthly invoices, monthly billing. Ends Nov 30, 2026. 25 spots in this batch.FILL25
Fill the Server, annual: about 29.63% off your first annual invoice. Ends Nov 30, 2026.FILL25Y
Fill the Server, 2 year term: about 15.69% off your first biennial invoice. Ends Nov 30, 2026.FILL25B
Fill the Server, 3 year term: about 11.11% off your first triennial invoice. Ends Nov 30, 2026.FILL25T
80% off your first 3 months, monthly billing. Ends Dec 25, 2027.3MONTHS80
50% off your first annual Shared term. Ends Dec 31, 2027.50SHARED
Shared Starter, 3 year term: C$105.84 total.MOOSE294
20% off your first 3 monthly VPS invoices. Ends Dec 31, 2027.20VPS3
25% off your first annual base VPS term.25VPS

← All guides

Security

Linux SSH hardening: reduce remote-login risk without locking yourself out

Published August 2026 · 2 min read · Updated 2026-09-05

SSH hardening is a sequence of access decisions: who may connect, which credentials are accepted, which network paths are exposed, how privileges are elevated, and how you recover when a key or configuration change goes wrong.

Create a recoverable administrator path first

Before disabling anything, prove a named administrative account can authenticate with its intended SSH key and elevate privileges. Keep the current session open while testing a second session so a typo does not become a lockout.

Know the provider-console or recovery route before changing SSH access on a remote-only server.

Prefer keys and minimize direct privileged login

Public-key authentication avoids sending a reusable password to the server and supports per-person credentials. Disable direct root login when the operating model supports a named account plus controlled privilege escalation.

Removing password authentication is useful only after every legitimate automation and operator has a working key path.

Limit exposure without confusing obscurity for security

A host firewall or upstream firewall can restrict SSH to expected source networks where practical. Changing the port may reduce noise but does not replace authentication, updates, logging, or rate controls.

Review authorized_keys and remove credentials that no longer have an owner.

Validate syntax and preserve auditability

Run sshd configuration validation before reload, then test new connections and sudo behavior. Monitor authentication logs and automate security updates according to the server’s maintenance policy.

  • Prove a second login before closing the first.
  • Use per-person SSH keys.
  • Keep a recovery-console path.
  • Validate sshd configuration before reload.

Next step

Harden SSH with keys, account controls, network policy and tested fallback access while keeping a recovery path before disabling working login methods.

Explore DotMoose VPS hosting

Keep reading

Related guides.

HTTP 500, 502 and 503 errors explained for website owners

Learn what HTTP 500, 502 and 503 errors usually indicate, which layer to investigate, what evidence to collect, and when restarting a service is not the real fix.

Read the guide

Linux file permissions: ownership, modes, groups and ACLs explained

Understand Unix ownership and rwx modes, then use groups and ACLs where needed so services can access files without opening them to every user.

Read the guide

Moving a DreamHost VPS to Canadian hosting

Inventory the server, copy it safely, test it, and cut DNS over with a rollback plan.

Read the guide

More vps & linux guides

We will handle the move. You check it first.

Your current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.

Start my free moveSee plans and prices
See pricesFree move