- cross-posted to:
- linux@programming.dev
- cross-posted to:
- linux@programming.dev
When you spin up a fresh public Linux instance, automated scanners start knocking on your doors within milliseconds.
It doesn’t take much to get locked down properly, but missing a few basics can leave you exposed.
I’ve put together a straightforward guide covering the essential hardening steps from UFW and SSH key-only auth to secure Docker bindings and automated maintenance.
Original content by The Unknown Universe, written by a human and not AI generated!



also for
why not just use
ssh-copy-id?edit: added more thoughts
You’re completely right on both counts, full-upgrade handles dependency shifts properly without leaving packages held back, and ssh-copy-id is much cleaner. Updated the guide to reflect both.
I love ssh-copy-id, but end up doing it manually about half the time anyway. I’ve tried integrating it into build scripts and find what the op did more reliable.
Could just be me though… it is Linux, and there a dozen ways to skin Linus. We all have our assholes and opinions.