Stage 8 · Lesson 1 of 9
Logging in with SSH
gives you a secure on another machine: ssh user@host logs you in. The first time you connect, SSH shows the server's , a kind of ID, and asks you to confirm it. It then saves it in ~/.ssh/known_hosts.
If SSH later warns that the fingerprint changed, the server may have been rebuilt, or something may be wrong. Log in with keys instead of passwords. ssh-copy-id user@host copies your into the server's ~/.ssh/authorized_keys file.
Your private key stays on your machine, with permissions set to 600. The keys you made for GitHub can work here too, though many people use a separate key for each purpose.
Common trapignoring a changed warning without finding out why.
A question to check yourself, an AI practice session and 2 cheat sheet entries come when you add the roadmap to your account. Add it
Resources for this stage
Start with· follow one of these
- GuideFreeInitial Server Setup with Ubuntu (DigitalOcean)
DigitalOcean · Beginner
A clear, widely used checklist for a new user, sudo, SSH access and a firewall on Ubuntu
- CourseFreeThe Missing Semester of Your CS Education
MIT · Beginner
The command-line environment lecture covers SSH, tmux, job control and dotfiles
Practise
Keep handy
Also worth your time
- roadmap.sh: LinuxGo deeper
The server, networking and troubleshooting branches of the Linux map