SSH
Keys, sshd_config, tunnels, passwordless login
Keys, sshd_config, tunnels, passwordless login
SSH is an encrypted channel to a server on port 22: you use it for a shell, file copies, admin panels that are closed to the outside, and git pushes. Server and user prove who they are with key pairs — and almost every SSH failure comes down to which key sits where.
Read the overview50-cloud-init.conf trap.ForwardAgent is riskier than it looks.localhost, without publishing a port.sshd_config, AllowUsers, the port or ufw rules, keep the current SSH session open and test the login from a second window.Check the server’s fingerprint before you answer yesOn the first login ssh shows the server key’s fingerprint and asks yes/no.Moving off port 22 cuts log noise but doesn’t protect youBots guess passwords on port 22; far fewer show up on another port.from SecretsEach key and token grants one accessEach key opens exactly one thing: a deploy key — one repository, a DNS token — the needed zones, a password — one service.Entries from other topics that are about this too.