Manage SSH access

Manage SSH access in Linux — with the four heights of help laid out: do it now, make it easier for the next person to accept, work out the right move when you are stuck, and learn the pattern so it stops coming back.

4prompt heights
Open it in the interactive atlas →

The four heights

The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.

Execute — do the immediate task

+
Grant SSH access to Miguel Ramos and Priya Shah for the web-prod servers. Add Miguel to the…
Grant SSH access to Miguel Ramos and Priya Shah for the web-prod servers. Add Miguel to the web-admins group and give Priya key-based access only. Sign on as root on server web-prod-01, verify their public keys in /etc/ssh/authorized_keys, set PermitRootLogin to no, and restart the SSH service. Confirm both can log in by 17:00 today and remove any expired keys first.

Improve — make it easier to accept

+
Before I open SSH for the new hires, make the access review easy for the security reviewer. Show…
Before I open SSH for the new hires, make the access review easy for the security reviewer. Show any accounts with password authentication enabled, surface keys that are older than 18 months, list which servers each user can reach, and flag any duplicate keys or root-capable entries so the reviewer can approve quickly.

Decide — diagnose the stuck moment

+
I added Aisha Khan's key to web-prod-02 and told her to test, but she reports immediate connection…

I just added a key to /etc/ssh/authorized_keys and now the user can't connect

I added Aisha Khan's key to web-prod-02 and told her to test, but she reports immediate connection refused. I checked sshd is running and the file permissions look correct. I can't see any relevant logs beyond a generic refused message, and I don't know if it's firewall, SSH config, or a bad key. What's the most likely cause and the quickest checks to unblock Aisha right now?

Become — change the pattern

+
Across the last six months we've spent hours fixing individual SSH failures: forgotten key…

We keep firefighting one-off SSH lockouts that eat evenings

Across the last six months we've spent hours fixing individual SSH failures: forgotten key rotations, root-enabled temporary access, and inconsistent group memberships. Each fix is urgent and undocumented. What one habit should we adopt to stop nightly lockout tickets, and what immediate change would remove at least half of these headaches within a month?

Next to this one

Other operating system work people do in Linux.

Every task here came from the work, not from a feature list — which is why the prompts name what you want done and never the button that does it. The tool changes; the work does not.
Copyright © LLOS.ai · 2026 — original pedagogy, voice, and design — all rights reserved.

The rest of the map

Same library, five ways in.