Re:Hacked. A Short Story
by olalonde on Monday January 19, 2015 @04:47AM
(#8911176)
Stories like this is what makes me believe immutable infrastructure is the future.
[ Parent
| on HN ]
Exactly. Does your business model care if your server is running apache or nginx? No? Then why the hell isn't that automated, baked, and tamper-proofed? We'll know we've arrived when the only feasible attack is sneaking malicious code into a git repo and hoping no one notices.
And that's why I'm quite excited by the concept of Coreos and the way they do updates.
curious to know how you can make a linux distro immutable from any modification.
Build a custom LiveISO.
There are plenty of tutorials, but it is boring to follow them manually, especially if you need to make a couple of tweaks to ISO or update it.
So I put together a couple of scripts to automate the process:
Get root, create a ramdisk, copy /usr/bin/* into it, and remount it under /usr/bin/*, and now you can do as you please.
Re:Hacked. A Short Story
by CiaranMcNulty on Monday January 19, 2015 @07:23AM
(#8911565)
By regularly redeploying or re-imaging. Exploits can only live for a certain timescale + you can lock down nearly every entry point (no need for SSH access for instance).
How do you redeploy without some sort of remote access?
Re:Hacked. A Short Story
by acveilleux on Monday January 19, 2015 @09:27AM
(#8912020)
You use cloud VM API and images that use something like chef or salt to configure themselves.
Basically, you destroy a VM and spin up a new one with one of your images, it will then use chef or salt to pull in its config.
SSH isn't needed then.
Toggle the Read-Only window on the floppy disk
That's probably why it's the future and not the present.