News for hackers. Stuff that matters.
Re: by prmoustache on Tuesday November 17, 2026 @03:03PM (#50537324)
I am not sure what is supposed to be wrong with puppet managed linux servers.
Re: by Nevermark on Tuesday November 17, 2026 @07:25PM (#50540252)
Say “puppet linux servers” really fast several times.

Yeah.

Re: by lrvick on Tuesday November 17, 2026 @08:44PM (#50540832)
Production servers should be hardened, immutable, and remotely attestable appliances. Everyone should be able to prove every line of code in memory at all times, with access to secrets gated on signed quorum approval from multiple reviewers. They should not have dev tools, ssh, a shell, and certainly not capable of blindly modifying themselves at runtime if a single admin of a Puppet control server asks them to. Such tactics mean a single compromised engineer laptop means a compromise of production, and thus a data breach is all but inevitable.

If someone even suggesting Salt, Puppet, or Ansible in a sysadmin interview today for production systems with a straight face I would fail them.

Re: by solyin on Tuesday November 17, 2026 @09:54PM (#50541273)
What's the hardened immutable infra you're using these days?
Re: by edf13 on Wednesday November 18, 2026 @02:16AM (#50542892)
Never worked with a legacy system?
Re: by prmoustache on Wednesday November 18, 2026 @02:47AM (#50543069)
I understand and subscribe to some of the things you say but:

> Such tactics mean a single compromised engineer laptop means a compromise of production, and thus a data breach is all but inevitable.

I hope you don't believe that an immutable image cannot be compromised. The commits done to the build system come from the same engineer laptops and, in a world where CVE are published ao frequently, said compromised image could be deployed largely in only a few minutes hours.

Also there is something to be said with lack of debugging tools. While I agree that reducing the surface of attack is the way to go, I am pretty sure the reason it takes so long for some of the big infra outages we have experienced from various cloud vendors comes from the inability of engineers to log on some systems, observe and potentially fix temporarily by hand to stop a race condition. There is often a race condition and serpent eating its own tail situation involved and logs might not even reach the monitoring infra anymore.

Going back to manage pets is not the way to go but I am not entirely certain removing ability for a subset of engineers to log on systems is exactly the way to go.