SSH lets you safely log into another computer over the internet and use it as if you were sitting in front of it. It stands for “Secure Shell”. Developers use it constantly to control servers far away.
The basic idea
You open your terminal and type:
ssh shravan@example.com
If all goes well, you are now typing commands on that remote computer. Your keyboard, their machine. The “secure” part means everything is encrypted, so nobody snooping on the network can read it.
Passwords vs keys
You can log in with a password, but the better way is using SSH keys. A key comes in two parts:
- a private key, which stays secret on your computer
- a public key, which you put on the server
The two parts match each other like a lock and key. The server checks them and lets you in, with no password typed each time.
ssh-keygen # make a key pair
Rule number one: never share your private key. It is private for a reason. The public one you can hand out freely.
Where you use it
- Logging into a server to deploy or fix something.
- Pushing code to GitHub (it often uses SSH keys under the hood).
- Copying files between machines with
scp.
Why it matters
Before SSH, people sent commands and passwords as plain text that anyone could read. SSH made remote work safe. So every time you quietly connect to a server and it just works, SSH is doing the hard, invisible job of keeping it secure.