Access safety checklist (0/6)Keep an existing SSH session and provider console open.Test a separate non-root sudo user with public-key login.Check firewall/security groups allow the chosen port before changing it.Back up config; inspect Include and Match precedence; test effective config.Apply rate limiting (for example fail2ban) and security updates separately.After reload, test a new connection before closing the original session.

Self-reported checklist only; completion does not prove host security.

SSH server portAllowUsers (optional local usernames, space-separated)Disable all root loginI tested a separate non-root public-key login and sudoDisable password and keyboard-interactive authenticationDisable X11 forwardingDisable TCP forwarding (breaks tunnels)

How to use this tool

Keep your current session and console, verify a separate key login, then review generated config before applying it manually.

When not to use it

No SSH connection or host audit. Include/Match precedence and distribution service names need manual checks. A wrong change can lock you out.

Finding these tools useful?

Your support helps me maintain the tools and keep the data up to date.

Buy me a coffee↗

g3n-data

Source-backed global references and browser-based developer tools.

About Methodology Guides Privacy Author ↗All links ↗