Esta página está disponible en español.
Ver en españolEngineering notes on running Linux fleets — security, operations and what we're building at CentralHost.
5 min read
Closing SSH to the world is the easy part. The reason people don't is fear of being locked out. Here's how to keep two ways in — everyday and emergency — and only then shut the door, using CentralHost's own firewall and bastion.
6 min read
A ticket lands where the only fix lives on the box — and the person who can fix it doesn't work for you. Sharing root or spinning up a temp SSH user are both bets you'll regret. CentralHost issues a one-time, time-boxed, audited terminal instead: the guest operates the server without ever holding a credential to it.
5 min read
A shell session is gone the moment you close it — no record of the commands, the output, or the order. This is why CentralHost records every operator terminal: not to watch anyone, but because a record beats your memory at 2am two weeks later.
4 min read
You have root on machines you don't own. Sooner or later a client asks what your team did in there — and "trust me" is not an answer. The difference between a defensive conversation and a five-second one is whether the work was recorded.
3 min read
A queue that grows on its own is rarely a mail-server problem — it's a compromised account. How CentralHost names the culprit mailbox, stops the bleed, and resets it behind an approval gate.
4 min read
Hardening sshd is not the same as removing it from the attack surface. Three levels, from key-only auth to closing the port entirely.