Every reseller eventually has to log into a Linux server. Not through cPanel, not through WHM, but through a real shell. SSH (Secure Shell) is the protocol that makes this possible, and OpenSSH is the most common open-source implementation of it. This article is the cheat sheet: what SSH is, when to use it, and the minimum you need to know to stop being afraid of the terminal.
Who should care
| Audience | Why SSH matters | Priority |
|---|---|---|
| VPS resellers | Full server control beyond control panels | Essential |
| Managed hosting clients | Can troubleshoot before raising tickets | High |
| Developers on shared plans | Access logs, restart services, debug | Moderate |
| Windows-only users | Requires PuTTY or Windows Terminal setup | Learning curve |
What happened
- SSH (Secure Shell) is a network protocol for securely accessing remote computers over unsecured networks.
- The SSH suite includes slogin, ssh, and scp, the secure successors to the older rlogin, rsh, and rcp UNIX utilities.
- Authentication can use passwords or public key cryptography.
- Linux and Mac have built-in SSH clients; Windows users typically use PuTTY.
- The SSH daemon listens on a configurable port (default 22) and negotiates the protocol version with the client at connection time.
Why this matters
SSH knowledge separates resellers who fix problems themselves from those who wait for upstream support. A task that requires multiple clicks through cPanel—say, diagnosing why a cron job is firing twice—takes under a minute in a terminal. That is the trade-off: a small upfront learning curve versus ongoing time savings every time something breaks outside the control panel.
The public-key angle is the one most resellers skip, and it matters most. Password-based SSH works for occasional use. For daily work, especially from a laptop that moves between networks, public-key authentication eliminates a class of security concerns. Set it up once, and you never type a password into SSH again.
Windows users face a small wrinkle. If you are on Windows, you are likely using PuTTY or Windows Terminal. PuTTY uses its own key format, which means the public-key setup is slightly different than on Linux or Mac. The steps are well-documented, and it is worth the effort.
What to watch next
Watch the industry-wide shift toward key-only authentication. Major cloud providers default to key-based SSH on new instances. If your upstream provider has not made that switch, expect it. Also watch the post-quantum cryptography conversation. SSH is not broken, but the migration to post-quantum key exchange is underway and will eventually reach OpenSSH defaults.
Key takeaways
- SSH is essential infrastructure knowledge for any reseller running their own servers.
- Public-key authentication is the right default for daily work; passwords are for emergencies.
- The Windows path through PuTTY is well-trodden; the key format is the only real wrinkle.
- Knowing SSH means fewer support tickets and faster fixes.
Frequently asked questions
Do I need SSH if I use cPanel?
Not for day-to-day account management, but you will need it for server-level work like fixing cron jobs, checking logs, or restarting services.
What is the default SSH port?
Port 22. Many providers change it for security reasons, so always check your welcome email.
Can I use SSH on Windows?
Yes, with PuTTY, Windows Terminal, or the built-in OpenSSH client on recent Windows builds.
What is the difference between SSH and OpenSSH?
SSH is the protocol. OpenSSH is the most common open-source implementation of it, used on most Linux distributions.
Is SSH only for Linux servers?
No. You can SSH from any operating system—Windows, Mac, or Linux—to access a Linux server. The client runs on your local machine; the server runs on the remote machine.